- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Thu, 02 Dec 2010 10:10:23 -0500
- To: Brad Kemper <brad.kemper@gmail.com>
- CC: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
On 12/2/10 10:01 AM, Brad Kemper wrote: > The text still appears to be contradictory. Maybe I'm not seeing your updated version? I don't know. Where are you looking? > What is it supposed to look like when the test doesn't fail? Grab http://test.csswg.org/svn/contributors/bzbarsky/submitted/css2.1/run-in/run-in-breaking-002-ref.xht (the reference) and save it locally. This is rendered identically in Gecko, Presto, Webkit and is the correct rendering of the test. This doesn't use run-ins and doesn't depend on correct handling of inline breaking; it simulates a line-broken inline using two inlines with a break between them. The grab http://test.csswg.org/svn/contributors/bzbarsky/submitted/css2.1/run-in/run-in-breaking-002.xht (the test) and save it locally. Load it in your browser of choice. It should look just like the other file. I believe that all three of Gecko, Presto, Webkit fail at the moment, for different reasons (e.g. Gecko not supporting run-in). Not sure about IE; haven't tested. -Boris P.S. If I save that second file as .html, then behavior seems to be non-interoperable. Gecko sees the "<![CDATA[" bit as part of the stylesheet data in HTML, and ignores some of the rules while Presto and Webkit do not. I'm not sure whether Webkit and Presto strip it out at the HTML parser level or the CSS parser level, but this seems like something we should have a test for if we don't have one yet.
Received on Thursday, 2 December 2010 15:10:59 UTC