- From: <lists@m8y.org>
- Date: Tue, 5 Feb 2013 12:48:01 -0500 (EST)
- To: www-style@w3.org
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.
Received on Tuesday, 5 February 2013 17:48:23 UTC