- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Nov 2023 23:14:53 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-values-4] Restrictions on UA-default viewport units (unprefixed v*)`, and agreed to the following: * `RESOLVED: Define how new and old viewport units interact and that old units are eq. to large viewport units` <details><summary>The full IRC log of that discussion</summary> <dael> TabAtkins: A while back when defining the set of viewport units there was a question what old version should be. The plain ones<br> <dael> TabAtkins: Defined as undefined but have to between small and large. I believe at the time UAs were inconsistent<br> <dael> TabAtkins: Now the test we performed seem to show unprefixed is large viewport is where people converged. Would like to spec that<br> <dael> astearns: Comments? Concerns?<br> <dael> astearns: I see some research. Do we have WPT?<br> <dael> TabAtkins: I believe research was based on WPT but we can make sure to cover<br> <dael> TabAtkins: Issue is difference between units only shows on mobile, but WPT coverage of mobile is underdeveloped. There is work on that<br> <dael> astearns: Prop: Define how new and old viewport units interact and that old units are eq. to large viewport units<br> <dael> astearns: Obj?<br> <dael> RESOLVED: Define how new and old viewport units interact and that old units are eq. to large viewport units<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6454#issuecomment-1789817599 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 November 2023 23:14:55 UTC