Gregory's ServerOr maybe you have better suggestions?
Requirements:
1. Name is derived from the id attribute (stretch req: any attribute)
2. Name is auto generated
3. First try 1, falling back to 2
|
Top-level
 5 comments
 @bramus "auto" already has meanings in CSS (width:auto, etc) which implies to me on first read that "auto" means "the default" or "what it would be if you hadn't said anything", which is very much not the same as "we will make up a sort of random string". So I don't like "auto" (I appreciate that "we make up a name" IS the "default" here so "auto" is technically correct, but it confuses me). The point about being auto-generated isn't that it's auto, it's that it's generated. name:generated? @bramus sure! I’m not really saying that it always is; as I say, “auto” is probably technically correct here. But I think the vague “meaning” of auto in people’s heads, and certainly in mine, is a sort of “go back to what it would be if you hadn’t said anything”, which doesn’t quite feel the same as “explicitly set a value but it’s the value we would use if you don’t express a preference”. @bramus I’m not quite sure I follow what’s being asked here. The stretch requirement would seem to suggest `attr()` should be used, but because you could be selecting multiple elements it’s a bit awkward. That didn’t stop CSS counters from doing similar stuff though 🤷♂️ It might be useful to see all the expected usecases laid out in an article 🤔 |
RT = Easier to handle View Transitions for all of you, soon!