[Edit: Never mind. Turned out my issues were due to top-level CSS that I wasn't overriding/accounting for, not the invalid markup.]
Man do I hate stuff like this. I'm working on putting some relatively simple content into an automated system that allows a block of user-supplied HTML.
The positive side of the template is that it will allow most HTML, and inline styles. "Oh, good," I think "I can just do some simple markup, inline the CSS, and I'm good." It's also XHTML 1.0 transitional, although their own makrup has a few errors.
Problem: The user-supplied HTML gets stuffed into a <span> element. Validity issues aside, this is having the side effect of munging up my applied styles to block-level (<p> and some floating <div>s) elements within.
I'm not trying to do anything fancy--a few paragraphs, a header, and a few floating images, all styled appropriately. The system is completely outside of my control, and <iframe> is also not an option--it won't allow that tag.
Am I overlooking some obvious workaround for this? Any suggestions of a way to get this working?
Man do I hate stuff like this. I'm working on putting some relatively simple content into an automated system that allows a block of user-supplied HTML.
The positive side of the template is that it will allow most HTML, and inline styles. "Oh, good," I think "I can just do some simple markup, inline the CSS, and I'm good." It's also XHTML 1.0 transitional, although their own makrup has a few errors.
Problem: The user-supplied HTML gets stuffed into a <span> element. Validity issues aside, this is having the side effect of munging up my applied styles to block-level (<p> and some floating <div>s) elements within.
I'm not trying to do anything fancy--a few paragraphs, a header, and a few floating images, all styled appropriately. The system is completely outside of my control, and <iframe> is also not an option--it won't allow that tag.
Am I overlooking some obvious workaround for this? Any suggestions of a way to get this working?