- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Aug 2023 23:46:32 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-contain-3] Add container-font relative units `, and agreed to the following: * `RESOLVED: Add these four container font relative units and their functional versions to target specific containers` <details><summary>The full IRC log of that discussion</summary> <dael_> miriam: We added cq units that are similar to viewport. cqi, cqv etc. several use cases for getting something like rems but relative to container. cqch, cqx [missed]. cqm and cqlh are clearest<br> <fantasai> sgtm<br> <dael_> miriam: Other question is this came from an issue we resolved by adding functions for cq units so you could access the unit on a specific container. We can consider that here.<br> <TabAtkins> q+<br> <dael_> miriam: Question is do we want these 4 cq relative units<br> <astearns> ack TabAtkins<br> <dael_> TabAtkins: I think this is reasonable. We also should put this into functional syntax. If you can access some aspects of an arbitrary container, getting to the font bits makes sense<br> <dael_> TabAtkins: +1 to the full proposal<br> <una> +1 this proposal makes sense!<br> <florian> s/cqx/cqex/<br> <florian> s/cqm/cqem/<br> <dael_> astearns: Prop: Add these four container font relative units and theri functional versions to target specific containers<br> <dael_> astearns: obj?<br> <dael_> RESOLVED: Add these four container font relative units and their functional versions to target specific containers<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8855#issuecomment-1663103733 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 August 2023 23:46:34 UTC