Closed Bug 1211330 Opened 9 years ago Closed 6 years ago

Remove CSS pref "layout.css.unset-value.enabled"

Categories

(Core :: CSS Parsing and Computation, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla63
Tracking Status
firefox63 --- fixed

People

(Reporter: dholbert, Assigned: mozbugz)

References

Details

Attachments

(2 files)

As heycam noted parenthetically in bug 1210905 comment 19:
> >  if (IsCSSPropertyPrefEnabled("layout.css.unset-value.enabled")) {
>
> (At this point it's probably safe to remove this pref...)

I take it this feature is mature/baked enough that there's no point in having it be pref-toggleable anymore.
I suspect this pref doesn't work at all now, I don't remember any code handling it on stylo.
See Also: → 1459524
Assignee: nobody → gsquelart
Comment on attachment 8988391 [details]
Bug 1211330 - Removed CSS pref layout.css.unset-value.enabled -

https://reviewboard.mozilla.org/r/253670/#review260588

::: layout/style/test/property_database.js:2765
(Diff revision 1)
>      "none, none, none, none, none",
>      "url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAIAAAD8GO2jAAAAKElEQVR42u3NQQ0AAAgEoNP+nTWFDzcoQE1udQQCgUAgEAgEAsGTYAGjxAE/G/Q2tQAAAABJRU5ErkJggg==), none",
>      "none, url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAIAAAD8GO2jAAAAKElEQVR42u3NQQ0AAAgEoNP+nTWFDzcoQE1udQQCgUAgEAgEAsGTYAGjxAE/G/Q2tQAAAABJRU5ErkJggg==), none",
>      "url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAIAAAD8GO2jAAAAKElEQVR42u3NQQ0AAAgEoNP+nTWFDzcoQE1udQQCgUAgEAgEAsGTYAGjxAE/G/Q2tQAAAABJRU5ErkJggg==), url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAIAAAD8GO2jAAAAKElEQVR42u3NQQ0AAAgEoNP+nTWFDzcoQE1udQQCgUAgEAgEAsGTYAGjxAE/G/Q2tQAAAABJRU5ErkJggg==)",
>      ].concat(validGradientAndElementValues),
> -    invalid_values: [
> +    invalid_values: [ "linear-gradient(unset, 10px 10px, from(blue))", "linear-gradient(unset, 10px 10px, blue 0)", "repeating-linear-gradient(unset, 10px 10px, blue 0)"

Let's put these in invalidGradientAndElementValues instead, so they can be reused in various properties that take CSS images.
Attachment #8988391 - Flags: review?(cam) → review+
Comment on attachment 8988391 [details]
Bug 1211330 - Removed CSS pref layout.css.unset-value.enabled -

https://reviewboard.mozilla.org/r/253670/#review260588

> Let's put these in invalidGradientAndElementValues instead, so they can be reused in various properties that take CSS images.

As discussed, I've added a separate patch, as it's not related to the pref and adds new tests.
Comment on attachment 8989312 [details]
Bug 1211330 - Moved 'unset' invalid values from background-image alone to shared invalidGradientAndElementValues -

https://reviewboard.mozilla.org/r/254370/#review261190
Attachment #8989312 - Flags: review?(cam) → review+
Pushed by gsquelart@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bd647d6acb5a
Removed CSS pref layout.css.unset-value.enabled - r=heycam
https://hg.mozilla.org/integration/autoland/rev/7ff340d8288f
Moved 'unset' invalid values from background-image alone to shared invalidGradientAndElementValues - r=heycam
https://hg.mozilla.org/mozilla-central/rev/bd647d6acb5a
https://hg.mozilla.org/mozilla-central/rev/7ff340d8288f
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
What dev docs need updating? There are no flags, quirks, or notes regarding unset in the browser compatibility charts. If I understand correctly, this fixed occurrences of unset making a css property fail when it shouldn't and not fail when it should fail.
Yeah, given that there's no mention of the pref in https://developer.mozilla.org/en-US/docs/Web/CSS/unset I don't see anything that needs to be done.
(In reply to Estelle Weyl from comment #11)
> [...] If I understand correctly, this
> fixed occurrences of unset making a css property fail when it shouldn't and
> not fail when it should fail.

This bug here removed the now-unused about:config preference 'layout.css.unset-value.enabled', and also improved the test coverage.
The 'unset' feature itself was not touched in this bug.
So as David confirmed, no docs should need updating.
Keywords: dev-doc-needed
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: