W3C home > Mailing lists > Public > www-style@w3.org > November 2009

Re: One more run-in question: replaced elements

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sat, 21 Nov 2009 09:23:36 -0600
Message-ID: <dd0fbad0911210723x65e33c65lac2188ee5e0bb47d@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: www-style list <www-style@w3.org>
On Fri, Nov 20, 2009 at 11:22 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> I just realized that there's one more interesting edge case: replaced
> elements styled with "display:run-in".
>
> Testcase:
>
> <!DOCTYPE html>
> <html>
>  <body>
>    <img style="display: run-in"
> src="http://www.mozilla.org/images/mozilla-banner.gif">
>    <div style="border: 20px solid green">aaa</div>
>  </body>
> </html>
>
> Observed behavior:
> Opera 10.01: Image does not run in.
> Webkit 2009-11-20 nightly: Image does not run in.
> IE8: Image runs in.
>
> The IE8 behavior seems correct to me, given the spec text, right.

I can see how the Opera/Webkit behavior is justifiable.  By definition
CSS knows nothing about the contents of a replaced element.  Thus we
have no idea whether it runs afoul of the various restrictions on the
content of the run-in element that will prevent it from running-in.

It's probably justifiable from spec to say "Well, if we don't know
anything about the contents, then they don't fit any of those tests by
definition", but I'm not certain that's the best behavior.

(I'm also not sure what the most desirable behavior is to me as an author.)

~TJ
Received on Saturday, 21 November 2009 15:24:23 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:22 GMT