christripledot - 11:39 am on Jun 14, 2011 (gmt 0) [edited by: alt131 at 12:00 pm (utc) on Jun 14, 2011]
I noticed that IE5/Mac doesn't seem to suffer from the hasLayout bug. In my case display: inline-table doesn't improve things, so I think I'm gonna stick with my solution. Although it uses unnecessary markup in the HTML, I prefer my CSS because IMO it is more readable. All the hacks are obviously related to containment. As soon as you start messing with things like inline-whatever, stuff can get ugly real quick.
Slightly OT, but I don't really see the issue with 'unnecessary' <span>s and <div>s in situations where there is no semantic alternative. Aren't these elements supposed to be 'content-neutral' (semantically, at least)? All the screenreaders I've messed with don't give a <snip> about <div>s.
In any case, who's ever tried to get under the bonnet with PDF accessiblity? What a can of worms... So many 'Artifacts' flying around the place; correcting the reading order sometimes messes with the z-index of drawn objects (esp. when clipping masks come into play); it's the stuff of nightmares.
Give me simple CSS and meaningless <div>s and I'm a happy man.
P.S. Thanks to all of your generous replies I now have a happy client :)
[edit reason] Tidy [/edit]
[edited by: alt131 at 12:00 pm (utc) on Jun 14, 2011]