On Fri, Mar 31, 2023 at 2:37 AM Chris Harrelson <[email protected]>
wrote:

> Contact [email protected]
>
> Specificationhttps://drafts.csswg.org/css-overflow-3/#valdef-overflow-auto
>
> Summary
>
> Removes the overflow:overlay scrolling mode, and makes overlay a legacy
> alias of auto. overflow:overlay is the same as overflow:auto, except that
> it does not prevent content from extending into the scrollbar gutter, in
> cases where non-overlay OS scrollbars are present. (If overlay scrollbars
> are present, there is no effect.) Example: With overflow:overlay:
> https://output.jsbin.com/yujenuq/quiet With overflow:auto:
> https://output.jsbin.com/ruzogaf/quiet
>

Which platforms would one see a difference between these two? (I'm not
seeing a difference on MacOS)


>
>
> Blink componentBlink>Scroll
> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EScroll>
>
> TAG review
>
> TAG review statusNot applicable
>
> Risks
>
>
> Interoperability and Compatibility
>
> Developers currently relying on content overlapping the scrollbar gutter
> would instead see some additional line wrapping. Users, on the other hand,
> would be able to see more content that is currently invisible underneath a
> scrollbar.
>

I'm assuming that content would avoid overlapping with the gutter before
scrolling ever starts, right? (rather than triggering layout shifts once
the user scrolls)


> On platform configurations with overlay scrollbars in the OS, this change
> has no effect; it only applies to situations where a non-overlay scrollbar
> is configured by the browser. Use counter:
> https://chromestatus.com/metrics/feature/timeline/popularity/2995
> Adoption is more than 2% of page loads.
>
>
> *Gecko*: Shipped/Shipping (
> https://github.com/mozilla/standards-positions/issues/768)
>
> *WebKit*: Shipped/Shipping (
> https://github.com/WebKit/standards-positions/issues/157)
>
> *Web developers*: No signals
>
>
> Debuggability
>
> Sites might not know why their line wrapping changed to exclude the
> scrollbar gutter. However, this is the existing behavior in Firefox and
> Safari, so they would get interop by default.
>
> Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, Chrome OS, Android, and Android WebView)?Yes
>
> Is this feature fully tested by web-platform-tests
> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
> ?Yes
>
> Flag nameOverflowOverlayAliasesAuto
>
> Requires code in //chrome?No
>
> Estimated milestones
> Shipping on desktop 114
> DevTrial on desktop 114
> Shipping on Android 114
> DevTrial on Android 114
> Shipping on WebView 114
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/5194091479957504
>
> This intent message was generated by Chrome Platform Status
> <https://chromestatus.com/>.
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-F4mOhUMuU3nw423C8CurZKX_wxQvXRPv-XT4Zhsm-XQ%40mail.gmail.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw-F4mOhUMuU3nw423C8CurZKX_wxQvXRPv-XT4Zhsm-XQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfWTkzPKzCF9gGdVHzXKVzDsv921OD-u_JTJv-muV3pkoQ%40mail.gmail.com.

Reply via email to