Tab Atkins Jr.
Tab Atkins Jr.
That makes sense. đź‘Ť
Agenda+ to check the group's temperature on this idea (and figure out what spec it would go in). To sum up: The problem to solve is bundling stylesheets together. (Particularly...
Again, we've historically preserved the single-dash idents for vendor prefixes, and there's no good reason for us to invade that space now. Please stop suggesting it. > Furthermore, could named...
The actual conflict is the fact that there's an `a/target` in SVG as well. You can see this in the data: ``` â•°â•´bikeshed refs --text=target --spec=svg2 --type=element-attr text: target displayText:...
These shouldn't be merged, imo. They're doing the same things, conceptually, but have a totally different set of controls for those things. We'd just have two divergent syntax branches, with...
And this should presumably use the same "same set of elements as the parent" semantic that implicit nested rules get (like `.foo::before { @media (...) { color: red; } }`),...
Hm, ok. I don't want to rely on pseudo-elements *never* being scoping roots, but if that's currently the case then the difference would be unobservable anyway.
That said, I've got a long-standing half-finished feature for doing translations of all the built-in strings. That would work for this, too.
Hmm, I'd rather just generate the same data (rather than reverse-engineer the ID format and hope the tool stays up). Looks like they do all the generation necessary in ,...
I could definitely see doing both. I think small lists would be listed inline, medium lists would be hidden in a `details`, large lists would be hidden *and* truncated, and...