News for hackers. Stuff that matters.
Re:Chrome 22 breaks things by cramforce on Friday September 28, 2012 @05:37PM (#4587916)
The spec says Chrome is right (was recently changed). Chrome is not the only browser. iOS browsers, the Android browser and Chrome for Android have always used the new behavior. The reason for the change is faster scroll performance, particularly on mobile.
Re:Chrome 22 breaks things by bzbarsky on Friday September 28, 2012 @11:27PM (#4588755)
Really? Can you point to the spec change? Did I miss a working group decision on this somewhere? Last I checked, the discussion on this got nowhere, with WebKit folks claiming this change was needed to optimize stuff and Opera and Mozilla folks claiming that optimizing scrolling worked just fine without this behavior change...
Re:Chrome 22 breaks things by cramforce on Saturday September 29, 2012 @01:36AM (#4588910)
Re:Chrome 22 breaks things by bzbarsky on Saturday September 29, 2012 @10:22AM (#4589633)
This has no such change. Try again.
Re:Chrome 22 breaks things by mark_story on Friday September 28, 2012 @11:02PM (#4588717)
Those are all webkit based browsers, so it seems normal that they'd all behave the same.
Re:Chrome 22 breaks things by cramforce on Saturday September 29, 2012 @01:36AM (#4588911)
Well they did not. Until Chrome changed the behavior to comply with http://www.w3.org/TR/CSS21/zindex.html
Re:Chrome 22 breaks things by mbrubeck on Saturday September 29, 2012 @10:48AM (#4589704)
The CSS 2.1 spec was last updated in 2011 and does not include any mention of this new stacking context behavior (which was only proposed on the CSS mailing list in May 2012 and has not yet made it into any spec).
Re:Chrome 22 breaks things by bzbarsky on Saturday September 29, 2012 @10:58AM (#4589739)
No, they changed it to no longer comply with that spec, actually. Please do read the spec, not assume it says what the "html5rocks" marketing folks want it to say.