- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Apr 2021 00:36:36 +0000
- To: public-css-archive@w3.org
> Yes, that is very much intentional, to solve the "interactive content underneath an overlay scrollbar" use case described in [#5232 (comment)](https://github.com/w3c/csswg-drafts/issues/5232#issuecomment-787614795). Right. What I'm saying is that we should use a different solution to this problem than `always`. According to my interpretation of the statement, this is the main reason the [webkit leads are not supportive](https://lists.webkit.org/pipermail/webkit-dev/2021-February/031708.html) of `scrollbar-gutter` right now: "Our opinion is that we don't want to encourage web developers to reserve space for scrollbars in a way that prevents non-interactive content from intruding into that space. This undoes a big advantage of overlay scrollbars, in that they leave more space for content." @smfr who wrote that comment. I propose we at least remove `always` for now, and then consider alternate solutions such as the `match-parent` value you suggested in #5232. -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4674#issuecomment-822884213 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 April 2021 00:36:38 UTC