Re: [csswg-drafts] [css-contain-3] "container width" and "container height" units (#5888)

The CSS Working Group just discussed `[css-contain-3] "container width" and "container height" units`, and agreed to the following:

* `RESOLVED: Use cq as the prefix`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-contain-3] "container width" and "container height" units<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5888<br>
&lt;dael> miriam: earlier resolved we wanted them and went back to give names. Can't give 'c'. Best I saw was 'q' units. q-width, etc.<br>
&lt;florian> I like "q*"<br>
&lt;dael> astearns: Some people in issue have concerns about mix with q typographical, but I don't think we should worry<br>
&lt;dael> TabAtkins: same<br>
&lt;dael> astearns: was cq- considered?<br>
&lt;dael> miriam: I don't remember seeing that<br>
&lt;dael> astearns: I don't know I'm going to argue in favor of it<br>
&lt;dael> jensimmons: We did have vh and now we have lvh. Don't know if that leads us anywhere with this<br>
&lt;dael> jensimmons: Kontainer :)<br>
&lt;dael> astearns: fantasai on irc says c doesn't add much<br>
&lt;dael> jensimmons: Something with q. Agree it's a little awk but q just as a letter is nice<br>
&lt;dael> astearns: Anyone that wants to argue against the spec approach of q?<br>
&lt;fremy> I feel like qw is liked becaue people use QWERTY keyboards ^_^<br>
&lt;dael> astearns: prop: Go with specified approach using q<br>
&lt;heycam> "queried width" reads well<br>
&lt;dael> plinss: We do have q unit<br>
&lt;fremy> Doesn't feel as special on AZERTY ^_^<br>
&lt;dael> astearns: We do. Was discussion in issue about possibility of confusion. I think people that understand what q unit is will not be confused. People who don't know won't know it exists<br>
&lt;dael> plinss: Concern with future name collisions<br>
&lt;dael> emeyer: That was my concer with future names<br>
&lt;dael> astearns: Future that spawn their own units<br>
&lt;dael> plinss: Last time we went through I raised concern on explosion of unit types<br>
&lt;RRSAgent> logging to https://www.w3.org/2021/10/06-css-irc<br>
&lt;dael> astearns: Do you have a solution? We seem to be proliferating unit types. I agree 2 letter names are sometimes difficult<br>
&lt;dael> plinss: Function<br>
&lt;emeyer> q+<br>
&lt;dael> fantasai: If people type function names in parens when they want to use a unit they'll be unhappy. We have units for a reason and abbreviate for a reason so we should continue. Agree we should avoid collisions but at least following a pattern<br>
&lt;dael> plinss: Want to make sure this really need to be a unit and not that we're doing it because we did it before. not saying that's case here but need guidance for next one<br>
&lt;emeyer> My muting has gone crazyz.<br>
&lt;emeyer> I do want to advocate for cq.  It’s more mnemonic.<br>
&lt;astearns> ack emeyer<br>
&lt;dael> astearns: emeyer advocates cq as the mnemonic. Does protect against possible future query units.<br>
&lt;emeyer> It would set a precedent of being more mnemonic with any future units.<br>
&lt;emeyer> That’s all from me.<br>
&lt;dael> astearns: Anyone that would object to using cq instead of merely q?<br>
&lt;TabAtkins> cq fine with me<br>
&lt;miriam> also ok with me<br>
&lt;fremy> cqw cqh sound fine<br>
&lt;dael> astearns: plinss you're okay adding these units because see need for them to be units but would like more guidlines of when units are necessary?<br>
&lt;dael> plinss: I don't have opinion on if these should be units. Haven't given much thought. I do want clear guidelines as to what should be a unit and why.<br>
&lt;dael> astearns: I think we need units b/c will use in same way as viewport units today.<br>
&lt;dael> astearns: I see comment from jensimmons ?<br>
&lt;dael> jensimmons: I wanted to see what it looked like<br>
&lt;dael> astearns: And what do you think?<br>
&lt;dael> jensimmons: Dunno<br>
&lt;dael> astearns: I think cq looks weird but may be because I looked at q for a while<br>
&lt;florian> I like the shorter version, but not to the point of blocking if we want to go the other way<br>
&lt;dael> astearns: I am swayed by future proofing to keep from future query units. cq provides distance from q unit<br>
&lt;dael> astearns: Prop: Use cq as the prefix<br>
&lt;dael> astearns: miriam okay with you?<br>
&lt;dael> miriam: Yeah<br>
&lt;dael> astearns: Objections to spec ch?<br>
&lt;dael> RESOLVED: Use cq as the prefix<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5888#issuecomment-937291693 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 6 October 2021 22:45:53 UTC