Closed
Bug 1623396
Opened 6 years ago
Closed 6 years ago
Custom props with invalid var() should behave as 'unset'
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla76
| Tracking | Status | |
|---|---|---|
| firefox76 | --- | fixed |
People
(Reporter: emilio, Assigned: emilio)
References
Details
Attachments
(1 file)
We have the same issue as chromium has, see bug 1623347.
Flags: needinfo?(emilio)
|
Assignee | |
Comment 1•6 years ago
|
||
See https://github.com/w3c/csswg-drafts/issues/4075.
There are tests that will get updated and this will make pass in bug 1623347.
|
||
Updated•6 years ago
|
Attachment #9134219 -
Attachment description: Bug 1623396 - Custom properties with invalid variable references should be unset, not initial. r=heycam,simonsapin → Bug 1623396 - Custom properties with invalid variable references should be unset, not invalid. r=heycam,simonsapin
|
|
Assignee | |
Updated•6 years ago
|
Flags: needinfo?(emilio)
|
|
Assignee | |
Updated•6 years ago
|
Priority: -- → P3
Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d49bad3acbc6
Custom properties with invalid variable references should be unset, not invalid. r=heycam
|
||
Comment 3•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox76:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
You need to log in
before you can comment on or make changes to this bug.
Description
•