Groups
Conversations
All groups and messages
Send feedback to Google
Help
Sign in
Groups
dev-platform@mozilla.org
Conversations
About
Intent to prototype and ship: Make -- a reserved custom property name
112 views
Skip to first unread message
Emilio Cobos Álvarez
unread,
Jun 4, 2021, 7:02:59 AM
6/4/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message as abuse
Sign in to report message as abuse
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Mozilla
Hi,
Summary:
In
https://github.com/w3c/csswg-drafts/issues/2692
it was resolved that
-- should be an invalid custom property name. I plan to try aligning
with that change in bug 1467309.
There's some compat impact study looking at httparchive (thanks Lea!) in
https://discuss.httparchive.org/t/how-prevalent-are-empty-custom-properties-in-css/2153/2
,
and I checked those pages and they seem like typos (the property is
defined, but never referenced, so there should be no rendering change).
So it seems worth a try.
Standard:
https://drafts.csswg.org/css-variables/#typedef-custom-property-name
Platform coverage: All
Preference: None
DevTools bug: N/A
Other browsers: We're the first ones in doing this, though I hope other
browsers would follow soon. I'll ping the relevant folks.
web-platform-tests: I changed the relevant WPTs in the patch.
-- Emilio
Reply all
Reply to author
Forward
0 new messages