Blink is the only other implementation of Variables currently, and they don't do variable fallback yet. I guess we should wait. Also we maybe should wait until we implement the CSSVariableMap part of the spec, which we don't yet.
Bug 950501 will probably resolve through spec, nevertheless IMHO this is a prerequesite before enabling. What about Bug 950264, Bug 950381, Bug 952338? Also: Adding Bug 773296 for good measure. (In reply to Cameron McCormack (:heycam) (away 24–25 Feb) from comment #0) > Also we maybe should wait until we implement the CSSVariableMap part of the > spec, which we don't yet. Is there a bug on file yet?
The working group agreed to take the spec to CR: http://lists.w3.org/Archives/Public/www-style/2014Jan/0604.html although it hasn't happened yet. We should try to get this shipped sooner rather than later.
Summary: unpref CSS Variables → ship CSS Variables (that is, enable the preference)
I agree. I spoke to Tab about Blink removing their implementation for the time being, and whether that should influence our decision to ship, and he was fine with us shipping. Bug 950436 should be fixed first, though. Let's not implement the CSSVariableMap stuff; I've indicated on www-style that I don't think we need it, and the [MapClass] stuff is going to be changed in Web IDL anyway.
Created attachment 8392760 [details] [diff] [review] patch Intent to ship email: https://groups.google.com/forum/#!topic/mozilla.dev.platform/wlc4FhqZBXA
Assignee: nobody → cam
Status: NEW → ASSIGNED
Attachment #8392760 - Flags: review?(dbaron)
Depends on: 985838
Comment on attachment 8392760 [details] [diff] [review] patch r=dbaron Can you track making sure Tab makes the spec edit for what goes insde var() functions, so that that doesn't get dropped?
Attachment #8392760 - Flags: review?(dbaron) → review+
The spec has already been changed to use <custom-property-name> in the syntax for var().
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla31
Florin, please make sure this gets assigned to the appropriate person for testing before release.
QA Contact: florin.mezei
Adding appropriate flag nominations so this can be tracked by QA and RelMan.
status-firefox31: --- → fixed
tracking-firefox31: --- → ?
relnote-firefox: --- → ?
I assume we will also want to relnote this?
tracking-firefox31: ? → +
(In reply to Benjamin Kerensa [:bkerensa] from comment #11) > I assume we will also want to relnote this? The flag is already set to relnote-firefox?
yup, relnote flag is up - thanks
I see all bugs that this depends on are already covered automatically. Is there anything needed from the Manual side?
Added in the release note for 31.
relnote-firefox: ? → 31+
Don't think any manual testing is required, thanks Florin.
You need to log in before you can comment on or make changes to this bug.