- From: Bramus via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Oct 2024 13:20:04 +0000
- To: public-css-archive@w3.org
For today’s breakout session, I think there are two paths forward: 1. Revert the previous `auto` resolution and use `auto` for the _“automatically generate me a name”_ case, because authors interpret that keyword as doing the latter. If so, we need to figure out a better keyword for the _“try to use the id attribute’s value and fall back to an automatically generated name”_ case or could leave it as is and push authors towards using `attr(id <ident>, auto)`. 2. Keep the previous `auto` resolution but come up with a _very_ good keyword that _clearly_ conveys that the name is automatically generated (which this issue is all about). Things to consider: - A poll with authors suggests that the keywords `from-element`, `per-element`, and `self` do not clear express _“auto generate me a value”_. Authors prefer `auto` or `auto-id` here. Some authors have suggested `generate(d)`. - Some authors have suggested the `attr()` approach without it being presented as an option (many did vote for the `first-non-empty()` thing). - Any new keyword that gets chosen must be specced as an invalid value for `view-transition-name`. This already is the case for `auto`. - The chosen keyword could potentially be exposed, depending on the outcome of #10995 _(do we expose the keyword, or the auto-generated id?)_ Something that just came to mind: the keyword that covers the _“automatically generate me a name”_ case can potentially be reused in the `ident()` function discussed in #9141 -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10995#issuecomment-2447129644 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 October 2024 13:20:05 UTC