<nobr> is an active formatting element for us in our WebKit nightlies,
and it has caused compat problems. Search for something in froogle to
see a nice big rendering error caused by us reopening <nobr> across a
</div>.
dave
Ian Hickson wrote:
On Mon, 11 Dec 2006, Anne van Kesteren wrote:
In current browsers <nobr> is different is treated differently from
other elements.
<nobr>1<nobr>2</nobr>3
gives:
E: nobr
T: 1
E: nobr
T: 2
T: 3
<nobr>1<div>2</nobr>3</div>
gives:
E: nobr
T: 1
E: div
T: 2
T: 3
This is quite different from "b", "strong", etc. and it probably has to
be this way too because of site compat.
I've tried to make <nobr> more compatible with IE (basically it implies a
</nobr> before itself). I'd be extremely interested in implementation
experience for this.
