Closed Bug 1195036 Opened 9 years ago Closed 9 years ago

@supports (text-combine-upright: all) incorrect

Categories

(Core :: CSS Parsing and Computation, defect)

43 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID
Tracking Status
firefox43 --- affected

People

(Reporter: bugzilla, Unassigned)

Details

(Keywords: testcase)

Precondition requisites ----------------------- - Use a recent Firefox 43 nightly built (say buildID = 20150815090753) - Set the about:config value of layout.css.text-combine-upright.enabled to true Self-explanatory tests ---------------------- http://www.gtalbot.org/BrowserBugsSection/CSS3ConditionalRules/supports-text-combine-upright-all.html http://www.gtalbot.org/BrowserBugsSection/CSS3ConditionalRules/supports-text-combine-upright-none.html Expected results ---------------- A red DOES NOT SUPPORT in the sentence is displayed Actual results -------------- A green SUPPORTS in the sentence is displayed Explanation ----------- Currently, Firefox has not implemented 'text-combine-upright: all' (that's bug 1097499) and it fails every single tests about 'text-combine-upright' that isn't testing default value or inheritance. If you repeat the steps above with Firefox 40.0 (stable release) buildID = 20150807094952, you will get expected results: a red DOES NOT SUPPORT I'm not confirming this bug report because I am no longer sure what @supports is actually supposed to report exactly or how in a real web page development this feature should be used to be relevant and useful.
Status: NEW → UNCONFIRMED
Ever confirmed: false
Keywords: testcase
@supports is supposed to test true if and only if the CSS parser keeps the declaration. Normally a UA would not keep the declaration if it does not support the property. Which is what we do. However, you toggled a debug preference which forces us to keep the declaration even though it does nothing. So the results you see are very much expected, since you explicitly asked the browser to act that way.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
When you say "you toggled a debug preference ...", you mean I toggled such debug preference by setting layout.css.text-combine-upright.enabled to true, right?
Yes. That preference is there to turn on the known-incomplete (and hence turned off by default) implementation so it can be debugged by the people working on it...
You need to log in before you can comment on or make changes to this bug.