- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Feb 2022 17:59:04 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `container name - string vs ident`, and agreed to the following: * `RESOLVED: Restrict container-name to just idents` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: container name - string vs ident<br> <TabAtkins> github: https://github.com/w3c/csswg-drafts/issues/6405<br> <TabAtkins> miriam: In the current spec we allow container names to be either a string or an ident.<br> <TabAtkins> miriam: Advantage of string is you can use attr() to take from the element and use it for a container name.<br> <TabAtkins> miriam: That could also be possible if browsers implement the extensions to attr() that let you specify the type, attr(foo ident)<br> <TabAtkins> miriam: Florian suggested just accepting ident would be easier<br> <astearns> ack fantasai<br> <TabAtkins> miriam: Don't have a strong opinion here. Like the flexibility, but would like browsers to implement attr() stuff<br> <TabAtkins> fantasai: Currently attr() is not only restricted to strings, but also just to the content property, so it'll require extensions regardless.<br> <bkardell_> kinda +1 to that<br> <TabAtkins> fantasai: So I think we can keep it ident-only, and when we extend attr() we can make sure it allows for idents as well.<br> <bkardell_> q+<br> <astearns> ack bkardell_<br> <TabAtkins> astearns: Not sure it follows we'd get attr() in this property and with 'ident' behavior at same time, but I suppose we'd have to either change attr() or change this property to allow strings.<br> <TabAtkins> bkardell_: +1 to fantasai about starting with ident.<br> <TabAtkins> bkardell_: I think attr() is a need in lots of use-cases way beyond this, feels bad to make an exception to solve one case.<br> <TabAtkins> q+<br> <astearns> ack TabAtkins<br> <Rossen_> q<br> <fantasai> TabAtkins: I think I'm the main defender of keeping string, but fantasai makes a good point that attr() isn't allowed anywhere at this point, so we'll fix it when we fix it, and I'm fine with ident for now<br> <TabAtkins> astearns: So hearing strong arguments for restricting to ident. Anyone wanna argue for strings?<br> <TabAtkins> astearns: Proposed resolution is to restrict to idents. We'll see if we need to add strings later, or if attr() is sufficient.<br> <bkardell_> s/ feels bad to make an exception to solve one case/ feels bad to make an exception to solve one case as a first option. It might be a thing we need to do, but it feels bad to start assuming that<br> <TabAtkins> RESOLVED: Restrict container-name to just idents<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6405#issuecomment-1049056338 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 February 2022 17:59:06 UTC