- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Sat, 03 Feb 2024 08:36:51 +0000
- To: public-css-archive@w3.org
emilio has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-overflow] Top layer containing block and scrollbar-gutter == It seems a bit weird to me that a test-case like this [live](https://crisal.io/tmp/scrollbar-gutter-top-layer.html): ```html <!doctype html> <html style="scrollbar-gutter: stable both-edges;"> <div style="width: 80ch; outline: auto;"> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. </div> <dialog id="dialog"> Woo </dialog> <button onclick="this.requestFullscreen()">Go fullscreen</div> <button onclick="dialog.showModal()">Show modal dialog</div> ``` Makes the fullscreen element not cover the whole screen / its containing block origin not start at zero, due to the scrollbar gutters. Maybe the top layer fixed-pos containing block should actually start at zero / ignore scrollbars on the root? It's a bit weird for regular fixed-pos elements too, for what is worth, but that behavior is consistent with `overflow: scroll` at least. cc: @fantasai @tabatkins @aethanyc @dholbert @smfr @nt1m @mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9904 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 3 February 2024 08:36:54 UTC