- From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Sep 2018 03:21:26 +0000
- To: public-css-archive@w3.org
@stephenmcgruer you say... > a scrolling box is created if "Elements and viewports have an associated scrolling box if has a scrolling mechanism..." In [CSS-overflow](https://drafts.csswg.org/css-overflow-3/#valdef-overflow-visible) > **visible** - There is no special handling of overflow, that is, the box’s content is rendered outside the box if positioned there. The box is not a scroll container. So I believe that all other [used] values for overflow (until implementation of the `clip` value https://github.com/w3c/csswg-drafts/issues/1971) create a "scrolling mechanism" according to spec. The `auto` value even creates a scrolling mechanism when not overflowing its content area. I think the current spec wording, though quite opaque, makes Chrome, Firefox, or Safari all spec compliant, in that as soon as an ancestor has `overflow` not set to `visible` in either axis, that ancestor has a "scrolling mechanism", even without overflowing its content area. Maybe the text "or it overflows its content area and the used value of the overflow-x or overflow-y property is hidden" should be removed to simplify/clarify? Have you read the linked issues/comments from my [previous response](https://github.com/w3c/csswg-drafts/issues/3083#issuecomment-418811715)? This https://github.com/w3c/csswg-drafts/issues/865#issuecomment-387908285 highlights your exact concern about "jumping sticky ancestors when layout changes". -- GitHub Notification of comment by jonjohnjohnson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3083#issuecomment-421219087 using your GitHub account
Received on Friday, 14 September 2018 03:21:27 UTC