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

RE: [CSS2.1] Flow control interop

From: Greg Whitworth <gwhit@microsoft.com>
Date: Mon, 17 Nov 2014 04:45:25 +0000
To: Robert Hogan <robhogan@chromium.org>, www-style list <www-style@w3.org>
Message-ID: <e2b55d7d8ae04c4eb91bd3d92505822c@BN3PR0301MB0868.namprd03.prod.outlook.com>
> In IE, it uses the negative value to put the 'clear' element 50px below the top of the block-formatting context. In Blink/WebKit/FF a negative value is chosen that allows the 'clear' element to sit directly under the float.
> So both behaviours are correct per the latitude allowed in the spec.
> Interoperability aside, in Blink's case I think the bug you've found is in case 2, where no clearance applies, and where Blink ought to place the 'clear' element 30px below the float just as it would with clear:none. That is a bug I will take and fix assuming no one points out an error in my understanding.
> To the broader question of choosing 'clearance' values that go as far down as possible vs starting at the bottom of the lowest float - I think it would be an easier and shorter process for IE to start matching all the others rather than the other way round. Again, unless there's a good reason not to. 

Agreed. Can someone from Webkit agree to make the same change to match Firefox on this testcase (http://jsfiddle.net/d83gt4d8/16/) since Blink has said they will make the change? IE will change our implementation as well to match FF but I want to ensure we have interop with Webkit/Blink as well before I submit the bug for implementation.

Rob could you please CC me on the CRbug that you open to make Blink interoperable with FF?

Finally, this change should be updated in the spec, should that go into errata or into a new CSS spec?


Received on Monday, 17 November 2014 04:46:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:48 UTC