| 13:53 | <annevk> | innovati: adding new global attributes does not necessarily increase the cost of creating an element; those things are highly dependent on the implementation |
| 13:54 | <annevk> | innovati: and it's quite likely we'll add new global attributes, we've added lots over the last decade or so |
| 13:54 | <annevk> | innovati: just look at WAI-ARIA |
| 13:55 | <annevk> | (and in fact, with data-* we've already accepted an infinity of global attributes) |
| 14:00 | <innovati> | Thanks @annevk! I'm exploring some CSS concepts and it seems like to target elements it would either need the creation of a bunch of new CSS selectors, or possibly a bunch of new HTML attributes that existing CSS selectors could target - for either situation the way you'd prototype something like that today would use data-* attributes to 'fake' it so it's just good to know what's possible while continuing to explore |
| 15:38 | <oliverdunk> | Domenic: RE https://github.com/whatwg/html/issues/4752, I think the concept isn't even mentioned in a way that a definition could be pulled from. I guess I was wrong using the word export - the concept just needs to be identified semantically using some sort of tag |
| 16:00 | <Domenic> | oliverdunk: they're identified using <dfn> tags, right? E.g. https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#attr-fe-autocomplete-family-name |
| 16:00 | <oliverdunk> | Domenic: Looking to refer to the full list of possible values, rather than a specific one |
| 16:01 | <Domenic> | oliverdunk: https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill-field |
| 16:02 | <oliverdunk> | Domenic: Hmm. I assumed that was referring to the attribute and not its values, but I think you're right :) |
| 16:03 | <oliverdunk> | Thanks for the help. |
| 16:04 | <Domenic> | :) |