- From: Gilmore Davidson via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Jan 2023 09:05:09 +0000
- To: public-css-archive@w3.org
So just to make sure I've understood this correctly... 1. Developers have been continually frustrated that there's no viewport unit that maps to the space remaining after scrollbars are added. This is because of the mental model summarised by @mor10 [in an earlier comment](https://github.com/w3c/csswg-drafts/issues/6026#issuecomment-881026696). 2. @brunoais puts together a well thought-out proposal in #6113 for dynamic viewport units. It includes an algorithm for resolving potential infinite layout cycles regarding scrollbars, specifically to address the problem in point 1. 3. The proposal is added to the CSS Values 4 spec. But browser vendors asked for the spec to keep the text "any scrollbars are assumed not to exist", so that it matched their implementations. Even though that line of text **completely defeats the purpose of the `dv*` units in the first place!** 4. A representative from a browser vendor effectively tells the original author of the proposal that the author doesn't know how the units are meant to work: https://github.com/w3c/csswg-drafts/issues/6026#issuecomment-1305449868 5. We all end up with **yet another** set of viewport units that don't solve this scrollbar problem, even though that's what they were meant to do. I can't speak for @brunoais, but I know that if I was in their position I'd be bloody furious about this process. To this outsider it's really not a good look for the treatment of external contributions. I come across sites and apps with unintended horizontal scrollbars like this almost daily. The most frustrating thing for me is that some browser vendors have previously said taking the scrollbars into account is close to impossible. Except Firefox has previously implemented that behaviour, so it's clearly possible to some extent. And as noted above, the original proposal outlined what to do to avoid infinite cycles. -- GitHub Notification of comment by gilmoreorless Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6026#issuecomment-1381508208 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 13 January 2023 09:05:11 UTC