- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Jun 2021 16:40:04 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Add lvh+lvw values`. <details><summary>The full IRC log of that discussion</summary> <Rossen_> topic: Add lvh+lvw values<br> <Rossen_> github: https://github.com/w3c/csswg-drafts/issues/6113<br> <bkardell_> ScribeNick: bkardell_<br> <TabAtkins> https://github.com/w3c/csswg-drafts/issues/4329#issuecomment-863677668<br> <TabAtkins> https://drafts.csswg.org/css-values-4/#viewport-relative-lengths<br> <bkardell_> TabAtkins: two weeks ago fantasai and I drafted new text for more viewport relative sizes. There was discussion about whether we should do some of these as env variables - we are currently using units<br> <bkardell_> TabAtkins: we introduced svw svh for small viewport, for example and a dvh for dynamic viewport ... as discussed in previous discussions dvh only needs to be accurate when it is stable<br> <bkardell_> TabAtkins: when the UI is stable, it is the correct size of the viewport<br> <bkardell_> TabAtkins: we would love comments or discussion - it's all very bikeshedable right now<br> <bkardell_> TabAtkins: if you have strong opinions on units vs env, let us know - we made an editors choice, but we can go either way<br> <bkardell_> TabAtkins: it would be great to be able to resolve on these next week (if we have the quorum)<br> <TabAtkins> ScribeNick: TabAtkins<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6113#issuecomment-871562263 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 June 2021 16:40:06 UTC