- From: Teodor Atroshenko via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Jul 2023 17:13:03 +0000
- To: public-css-archive@w3.org
This is a thoughtless solution to an entirely made-up problem. [87% of page loads](https://chromestatus.com/metrics/css/timeline/popularity/105) use some form of overflow on their page, do we know how many are `overlay` and if we don't then how can this decision be made? This change is very effectively degrading user experience across hundreds of UI frameworks that contain lightboxes (image galleries) and overlay dialogs. Most use `overflow: hidden` when displaying overlays to hide the irrelevant scrollbars which display above content, followed by unsetting the `overflow` property when overlay is hidden. **With this alias degradation there are now millions of devices running Chrome browsers wasting their CPU cycles on layout recomputes in response to pointless reflows caused by the lack of overlay scrollbars.** Similarly, loading screens (aka splash screens) of web apps are affected as there is an immediate layout shift once the splash screen is hidden leading to a terrible first impression. **As of today, July 11, 2023, there are no CSS-only alternatives to <body> `overflow: overlay` implemented by any browser.** -- GitHub Notification of comment by thexeos Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6090#issuecomment-1631192653 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 July 2023 17:13:05 UTC