- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Apr 2021 23:53:09 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `viewport propagation of scrollbar-gutter`, and agreed to the following: * `RESOLVED: We propagate scrollbar-gutter from the root to the viewport` * `RESOLVED: Scrollbar-gutter does not propagate from <body>` * `RESOLVED: No future properties should propagate from <body> to the ICB` * `RESOLVED: deprecate any existing use of body propagation` <details><summary>The full IRC log of that discussion</summary> <Rossen__> Topic: viewport propagation of scrollbar-gutter<br> <Rossen__> github: https://github.com/w3c/csswg-drafts/issues/6079<br> <myles> chrishtr: when you apply properties on the HTML or body elements, under certain conditions, ti gets propagated to the root element's scroller. Does this apply to scrollbar gutter properties? Proposed: yes.<br> <myles> Rossen: This is reverse propagation thing for overflow and direction<br> <myles> fantasai: Overflow doesn't inherit so it's less bad<br> <Rossen__> ack fantasai<br> <myles> fantasai: I absolutely hate body propagation rules in CSS. They should die. The web depends on them. I don't want it to propagated from teh body to the viewport<br> <tantek> +1 fantasai<br> <myles> emilio: Right. The scroll-snap stuff, and the thing that allows you to do smooth scrolling, those don't propagate.<br> <fantasai> s/The web/But the web/<br> <myles> chrishtr: If the user puts overflow on the body, and <missed> then they're just out of luck?<br> <myles> florian: They should put it on the root instead.<br> <fantasai> s/to the viewport/to the viewport. But we do need to specify that it propagates from the root to viewport./<br> <myles> florian: Putting things on HTML instead of body causes no problem. It's confusing if you've put it on body and it works, but you want to put other stuff on body but it doesn't work<br> <tantek> +1 florian, can we deprecate putting it on body so it's still "supported" but warned in CSS validators?<br> <myles> Rossen: let's go back to the actual issue here<br> <myles> Rossen: There's a proposal here about scrollbar gutter.<br> <myles> Rossen: For better or worse, we have behavior today that does the propagation<br> <myles> Rossen: Can we make that work for scrollbar gutter as well<br> <myles> florian: There are 2 potential resolution. The first is required. Propagate from the root to the viewport is required. Whether or not we ALSO propagate from the body is controvertial<br> <tantek> +1<br> <myles> fantasai: Let's resolve that we propagate from root to viewport first.<br> <myles> Rossen: Any objections?<br> <myles> RESOLVED: We propagate scrollbar-gutter from the root to the viewport<br> <myles> Rossen: Now what about body?<br> <myles> Rossen: It still works everywhere. I think our mutual feelings are the same.<br> <heycam> q+<br> <myles> fantasai: We're not saying that it should stop working on overflow. W'ere saying we shouldnt' add more properties to that list<br> <chrishtr> q+<br> <tantek> can we instead introduce an informative WARNING about depending on <body> propagation? (i.e. that devtools could flag for example)<br> <myles> emilio: There was a huge discussion years ago in gecko and other browsers. Gecko only propagates overflow and .....<br> <myles> florian: Overflow, background, and writing mode<br> <myles> emilio: Browser do differen things. Fancy new properties dont' propagate. Let's leave it as it is. Not propagate from body to root.<br> <tantek> +1 emilio<br> <florian> s/writing-mode/principal writing mode (i.e. writing-mode and direction)/<br> <fantasai> tantek, I'm happy to warn about it for the properties which currently do propagate (overflow/background/direction/writing-mode). But I *do not* want to add more properties to that list.<br> <tantek> fantasai, 100%<br> <myles> emilio: A lot of other properties dont' eitehr<br> <myles> iank_: Overscroll behavior does.<br> <myles> emilio: Scroll snap does<br> <myles> emilio: Those only work on the root<br> <myles> emilio: If UAs want to add a warning, if you detect you ahve a body that's not scrollable and it has scroll properties, they can log them to the console, that would be helpful, but let's not add more propagation<br> <myles> Rossen: It's less worse to put your custom scroll bar ... is to not have the appropriate space for it, so you're risking to have some broken UI experience in this case<br> <Rossen__> q?<br> <myles> florian: If you apply a property and it doesnt' do what you want then ... <missed><br> <florian> s/... <missed>/you fix your code/<br> <Rossen__> ack heycam<br> <myles> heycam: I was going to askw hat the specific list of scrollbar related properties is that currently propagates from body to the viewport. I don't wnat to end up in a situation where some scrollbar related things propagate but others don't. If scroll snaping and scrollbar color and scrollbar width propagate, then that's good<br> <tantek> A-ha "scrollbar-color value set on the HTML body element are not propagated to the viewport." https://drafts.csswg.org/css-scrollbars-1/#scrollbar-color<br> <fantasai> s/propagate/propagate don't propagate/<br> <myles> chrishtr: I'm okay with the not body thing.<br> <myles> chrishtr: That shortens the conversation<br> <myles> Rossen: I'm okay with this.<br> <myles> Rossen: Anyone else want to keep it?<br> <myles> Rossen: Objections?<br> <tantek> can we generalize that to any future scroll-*?<br> <myles> RESOLVED: Scrollbar-gutter does not propagate from <body><br> <myles> fantasai: Tantek is asking "can we generalize ..."<br> <tantek> yes please fantasai<br> <myles> fantasai: The proposed resolution is "don't propagate anythign else ever"<br> <myles> chrishtr: Do we need a resolution for scrollbar-width and one other?<br> <tantek> s/else ever/else ever from BODY to viewport<br> <myles> emilio: Those already don't propagate<br> <myles> Rossen: I think that was the generalized proposed resolution that fantasai said<br> <fantasai> chrishtr, they do propagate from the root already<br> <tantek> no more BODY propagation<br> <myles> Rossen: "Anything outside of overflow, direction, and background should not propagate from body"<br> <myles> florian: In addition, we need to propagate some things from HTML to the viewport<br> <myles> florian: Otherwise you can't change the scrollbar width<br> <myles> Rossen: I'm talking about <body><br> <myles> florian: We should open a new issue about which things need to be propagated and are missing<br> <myles> fantasai: Proposed resolution: no future properties will propagate from <body> to the ICB<br> <tantek> +1<br> <myles> chrishtr: I'll open a new issue about scrollbar-width on the HTML element<br> <florian> s/to be propagated /to be propagated from :root/<br> <myles> Rossen: No new objectsion<br> <fantasai> chrishtr, the spec already defines this<br> <fantasai> chrishtr, see https://drafts.csswg.org/css-scrollbars-1/#scrollbar-width<br> <fantasai> chrishtr, no need to open an issue...<br> <myles> RESOLVED: No future properties should propagate from <body> to the ICB<br> <chrishtr> fantasai, great!<br> <tantek> even current properties that don't say they propagate too right?<br> <fantasai> s/ICB/ICB or viewport/<br> <myles> fantasai: Tantek said something in IRC<br> <myles> tantek: proposal: deprecate, or add a warning, to any existing use of body propagation. This would enable CSS validators and dev tools to warn and flag when they depend on that behavior<br> <myles> emilio: I don't feel strongly. but sure.<br> <myles> emilio: Dev tools can warn for whatever without anything in the spec<br> <myles> emilio: We warn for stuff that doesn't apply. Saying "this is bad and you should feel bad" is not good<br> <myles> fantasai: I'm fine with deprecating and making that a statemetn so it can make its way to author-facing materials<br> <myles> fantasai: Deprecating settings values on <body> with the expectation it propagates to root<br> <myles> florian: Making it officially bad. "please don<br> <myles> florian: 't do this"<br> <myles> RESOLVED: deprecate any existing use of body propagation<br> <fantasai> scribenick: fantasai<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6079#issuecomment-816307011 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 April 2021 23:53:11 UTC