Previous Message
Next Message

strict vs. transitional doctype and rendering differences

Sent by Ingo Chao on 5 January 2010 06:06

2010/1/4 Bruno Fassino [EMAIL-REMOVED]>:
> I believe the difference in the rendering is related to the fact that
> in strict mode an element (in this case the red span) always generates
> an inline box (using its current font properties), like it always
> contained at least a character, even if it does not directly contain
> text.  Indeed adding a character
>  <div><span>a <em>Text</em></span></div>
> the difference in the rendering disappear.
> This Mozilla page [1], rather old, does not mention other differences
> caused by the "almost standard" mode. And I assume that the one that
> it mentions is the same I tried to describe (probably in a rather
> imprecise way...)
> Bruno
> [1]

2010/1/4 Jukka K. Korpela [EMAIL-REMOVED]>:
> a) whether the differences in rendering really matter (and it's not just a
> matter of an obsession of having the same rendering in all browsers)

Thanks to all!

I was asking because of the transition from transitional to strict
(html5) doctype for an (iframed) site. These nested inline elements
are used as hooks for background-images/sprites, so exact matching
heights are critical. No big surprise that these fragile constructions
break sooner or later.



So it is an "almost standards mode" problem, triggered by the
transitional doctype [2]?

The inner inline-block is sitting on a baseline in strict, and in
transitional, it doesn't [3].

Great, thanks!

css-discuss [EMAIL-REMOVED]]
List wiki/FAQ --
List policies --
Supported by --
Previous Message
Next Message

Message thread: