W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2017

[csswg-drafts] [css-overflow] how should ignoring overflow on the *-start sides of the scrollport be done?

From: L. David Baron via GitHub <sysbot+gh@w3.org>
Date: Thu, 23 Nov 2017 01:02:01 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-276243274-1511398915-sysbot+gh@w3.org>
dbaron has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-overflow] how should ignoring overflow on the *-start sides of the scrollport be done? ==
There's a longstanding interoperability issue relating to overflow that I really thought we'd discussed before, but I can't find any record of it.

Scrollbars provide a user interface that allows scrolling to overflow extending past the inline-end and block-end sides of the box.  However, overflow that extends past the inline-start and block-start sides of a box with `overflow:scroll` or `overflow:auto` is ignored.

Currently [the spec says](https://drafts.csswg.org/css-overflow-3/#scrolling-direction):
> Due to Web-compatibility constraints (caused by authors exploiting legacy bugs to surreptitiously hide content from visual readers but not search engines and/or speech output), UAs must clip the scrollable overflow region of scroll containers on the block-start and inline-start sides of the box (thereby behaving as if they had no scrollable overflow on that side).

This was introduced in [01821f08744d](https://hg.csswg.org/drafts/rev/01821f08744d524d6d532462444f3ef7912198e6), by fantasai, in January 2016.

This behavior description matches what Gecko and Edge do.

However, Chromium and WebKit have always done something different, which I believe is that if a box is entirely off of either the block-start or inline-start side of a box, that it makes no contribution to the box's overflow.

The difference matters when there's a box that is entirely before the inline-start (block-start) side of a box, but extends past its block-end (inline-end) side.  In that case, Gecko and Edge show a scrollbar, but Chromium and WebKit do not.

I'd like us to explicitly agree that we should do one or the other of these behaviors, and have the spec reflect it.

See also [Mozilla bug 1419142](https://bugzilla.mozilla.org/show_bug.cgi?id=1419142).

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2006 using your GitHub account
Received on Thursday, 23 November 2017 01:02:07 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:30:40 UTC