W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2018

[csswg-drafts] [css-position][css-sticky] Scrolling ancestor should probably include overflow:hidden even when content doesn't overflow

From: Stephen McGruer via GitHub <sysbot+gh@w3.org>
Date: Wed, 05 Sep 2018 15:45:23 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-357291399-1536162314-sysbot+gh@w3.org>
stephenmcgruer has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-position][css-sticky] Scrolling ancestor should probably include overflow:hidden even when content doesn't overflow ==
The spec[1] states that "the offset is computed with reference to the nearest ancestor with a scrolling box, or the viewport if no ancestor has a scrolling box." where a scrolling box is created if "Elements and viewports have an associated scrolling box if has a scrolling mechanism or it overflows its content area and the used value of the overflow-x or overflow-y property is hidden." [2]

This is not the behavior implemented by any web-browser. Scrolling the viewport on http://output.jsbin.com/yaxovep in any of Chrome, Firefox, or Safari shows that the sticky element is sticking to the overflow:hidden ancestor for both scrollers, even in the left-hand case where the content area isn't overflowed.

Rather than change all three browsers to follow the spec (which would also be an awkward change imo since you would end up jumping sticky ancestors when layout changes), we should change the spec I think.

@flackr 

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3083 using your GitHub account
Received on Wednesday, 5 September 2018 15:45:24 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 September 2018 15:45:25 UTC