- From: Felipe Erias <notifications@github.com>
- Date: Sun, 21 Jun 2020 18:44:25 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 22 June 2020 01:44:37 UTC
Thank you very much for your feedback. Regarding @alice's question about `stable` not being the default, my personal assumption is that doing so would break existing layouts so it is safer if `scrollbar-gutter` is an opt-in property. As the discussion and implementation get started, a couple issues have come up: - `scrollbar-gutter` is an inherited property, which might have unintended consequences for layouts. https://github.com/w3c/csswg-drafts/issues/5231 - some layouts are not possible with the current spec. For example, having headers and dividers that span the whole width of a list. https://github.com/w3c/csswg-drafts/issues/5232 In that last issue there is a mention about having _"an `env()` way of accessing the computed scrollbar size for solving these cases"_ which links with @atanassov's mention of getting more information and events about the scrollbar. I see `scrollbar-gutter` as a first step for solving the most common use cases, keeping in mind that eventually there might be a need for more elaborated solutions in some scenarios. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/520#issuecomment-647220234
Received on Monday, 22 June 2020 01:44:37 UTC