Closed
Bug 1312328
Opened 8 years ago
Closed 8 years ago
Remove CSS pref "layout.css.variables.enabled"
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla55
People
(Reporter: xidorn, Assigned: TYLin)
References
Details
(Keywords: dev-doc-complete)
Attachments
(1 file)
CSS Variables has been enabled since Firefox 31. We should remove this pref.
Even if we do not remove it, it would not control CSS Variables in stylo.
Updated•8 years ago
|
Keywords: dev-doc-needed
Updated•8 years ago
|
Priority: -- → P3
Comment 1•8 years ago
|
||
Mass wontfix for bugs affecting firefox 52.
Comment hidden (mozreview-request) |
Assignee | ||
Comment 3•8 years ago
|
||
Assignee: nobody → tlin
Status: NEW → ASSIGNED
Reporter | ||
Comment 4•8 years ago
|
||
mozreview-review |
Comment on attachment 8855594 [details]
Bug 1312328 - Remove CSS variables preference "layout.css.variables.enabled".
https://reviewboard.mozilla.org/r/127448/#review130164
Looks good, thanks.
Attachment #8855594 -
Flags: review?(xidorn+moz) → review+
Pushed by tlin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/07435005e74a
Remove CSS variables preference "layout.css.variables.enabled". r=xidorn
Comment 6•8 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Comment 7•8 years ago
|
||
bugherder |
Comment 9•8 years ago
|
||
I've added a note to the relevant browser compat info about this
https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_variables#Browser_compatibility
https://developer.mozilla.org/en-US/docs/Web/CSS/var#Browser_compatibility
I've also added a note to the Fx55 rel notes:
https://developer.mozilla.org/en-US/Firefox/Releases/55#CSS
Let me know if you think that covers it, or if anything else is needed. thanks!
Keywords: dev-doc-needed → dev-doc-complete
Assignee | ||
Comment 10•8 years ago
|
||
Chris, the documentation changes look good to me. Thanks.
You need to log in
before you can comment on or make changes to this bug.
Description
•