- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Jan 2023 07:38:20 +0000
- To: public-css-archive@w3.org
> TabAtkins: New functional unit is brand new syntax. Not a problem, but just for conservitiveness I think we want to lean existing pattern. I would think takes cq-length and contextually interprets based on cintainer name as other argument I strongly disagree with `container-reference(10cqi, card)`. Precisely, making lengths context-depend would be the complete opposite of an existing pattern. I think it will be very confusing and problematic, and I don't see any need to do that. Like, if `container-reference(10cqi, card)` is valid, is `container-reference(calc(10cqi), card)` also valid? And `container-reference(calc(10cqi + 0px), card)`? Does it accept any `<length>`? What does it do for other units? I'm fine with `container-reference(10, cqi, card)` or `container-reference(10 cqi, card)` or `calc(10 * container-reference(cqi, card))`. But passing a length seems to open an unnecessary can of worms. My preference is for `10cqi(card)` or `calc(10 * cqi(card))`. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7858#issuecomment-1371876234 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 January 2023 07:38:22 UTC