Hmmm. Do you have a screenshot of this?
Try this:
.post { display: block; width: 100%; overflow: auto; overflow-x: auto; overflow-y: hidden; }
Tested in IE 6, Opera 9.23 and Firefox 2.0.0.6 on the PC
Didn’t test it on IE 7 though, so you might want to look at that…
cb
@SamBauers:
Just to clarify your point, the reference cited for serving XHTML as text/html is quoted as a note from the current working draft of the XHTML 1.1 from February 2007. It’s not a standard as of yet and I don’t think it should be followed as such.
As for your point about IE borking with application/xhtml+xml, it absolutely is an issue. Hence, the point about serving the correct DOCTYPE based on the user agent. I’m no PHP guru by any means, so I had to get help in writing the logic to detect the user agent and what content type it could handle, but I know it’s possible as I’m using this mechanism on my site at this time.
@benbeltran: As for this not being important, I’ll leave that issue for now as I’ve seen way too many discussions spiral off into endless debate. The point is clear though: XHTML served as text/html is tag soup and IE doesn’t like XHTML as application/xhtml+xml. What do you do? Content negotiation or serve it as HTML 4.01 Strict as text/html. IMHO, this is the proper way of dealing with this.
I will check out this project and try to show you what I’m talking about. In class now, so I have to fly. . .
Hey _ck_.
Actually, I think it’ll be more useful when <!DOCYPE HTML> is used and widely supported by user agents, but that’s a whole other story. (http://www.whatwg.org/specs/web-apps/current-work/#the-doctype)
My point was more about serving up the correct content type, based on the DOCTYPE used. Serving XHTML 1.1 as text/html merits no benefits. It’s tag soup.
I would think that at least using some sort of content negotiation based on the user agent (serving HTML 4.01 Strict versus XHTML 1.1) would be a good start.
