- From: Ben Mathwig via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Apr 2021 17:23:23 +0000
- To: public-css-archive@w3.org
Just to follow up on this from the meeting: Simplifying scrollbar-gutter down to just auto and always makes the intent of the developer clear. If scrollbar-gutter is requested, the intent of the author is most likely to provided cross-UA reservation of scrollbar space regardless of classical or overlay scrollbars. In the case of stable, the use case here is only to solve for the scrollbar pop from overflow: auto in y-axis alignment of UI elements. The author may apply padding or margin to a non-scrollbar container above the scrollable container to match the gutter, but would have to conditionally remove this if the UA implemented overlay scrollbars. Using always instead would guarantee alignment without having to differentiate between UAs with classical scrollbars and with overlay scrollbars. In the description of scrollbar-gutter it states: The scrollbar-gutter property gives control to the author over the presence of scrollbar gutters separately from the ability to control the presence of scrollbars provided by the overflow property. The values stable and force seem intricately dependent on the overflow property, which voids the description of being separate from the overflow property. This is why I think we should drop everything except auto and always. -- GitHub Notification of comment by bmathwig Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4674#issuecomment-824229362 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 April 2021 17:23:25 UTC