- From: Johannes Odland via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Jul 2021 07:09:03 +0000
- To: public-css-archive@w3.org
> @tabatkins and I just committed the [changes](https://github.com/w3c/csswg-drafts/commit/0f78ba4ee462bf3ea879a122789dc153780b88f6) for this. We named the unit `sv*` (small viewport) and also added `dv*` (dynamic viewport) per #6113 > The changes should show up in the ED soon: https://drafts.csswg.org/css-values-4/#viewport-relative-lengths It is so good to se progress on this issue. Thank you! The floating browser chrome of Safari 15 might introduce some new complexity. There is some ambiguity towards what could be considered the large and the small viewport. There are suddenly not two but three sizes that are of interest: When browser chrome is floating: * The height of the whole screen including the area behind and below the floating chrome (the largest area) * The height of the area above the floating chrome (the smallest area) When browser chrome is collapsed in the bottom: * The height of the area above the collapsed browser chrome I would expect the large viewport to be the area behind the floating chrome. If I were to use the units to size images to fill the entire screen, this is the area I want to fill, even though there is browser chrome floating above. The small viewport though, would that be the area above the floating chrome (the smallest area), or the area when the browser chrome is collapsed at the bottom of the screen? -- GitHub Notification of comment by johannesodland Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4329#issuecomment-871985277 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 July 2021 07:09:05 UTC