W3C home > Mailing lists > Public > www-style@w3.org > February 2013

Re: position fixed, z-index and Google Chrome.

From: Simon Fraser <smfr@me.com>
Date: Tue, 05 Feb 2013 11:09:49 -0700
Cc: www-style@w3.org
Message-id: <0FD3ED7E-EF67-4B51-BE76-E384E0172117@me.com>
To: lists@m8y.org
On Feb 5, 2013, at 10:48 AM, lists@m8y.org wrote:

> On Tue, 5 Feb 2013, Simon Fraser wrote:
> 
>> On Feb 5, 2013, at 9:04 AM, lists@m8y.org wrote:
>> 
>>> So.  http://m8y.org/tmp/chrome_wtf.xhtml
>>> Is a mockup of a problem I encountered recently.
>>> 
>>> I was told to bring this up here.
>>> How does Chrome expect us to workaround this behaviour?  Or are we just not supposed to implement layouts like this anymore?
>> 
>> What is the exact problem that you're seeing? How does Chrome's behavior differ from other browsers?
> 
> Appears to be related to:
> http://updates.html5rocks.com/2012/09/Stacking-Changes-Coming-to-position-fixed-elements
> 
> The page has instructions to reproduce on it, did you try them? I can take screenshots if that helps.

Indeed. WebKit creates stacking context for position:fixed, in order to optimize scrolling. This is not strictly compatible with the spec, but was thought to have minimal real-world impact.

Simon
Received on Tuesday, 5 February 2013 18:10:23 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:05 GMT