Closed Bug 1520020 Opened 2 years ago Closed 1 year ago

Filter functions, e.g. blur(), brightness(), contrast(), ..., could be used without arguments

Categories

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

enhancement

Tracking

()

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: boris, Assigned: violet.bugreport)

References

(Blocks 1 open bug, )

Details

(Keywords: dev-doc-needed)

Attachments

(1 file)

Based on the updated spec [1], if we omit the arguments in these css filter functions (blur(), brightness(), contrast(), grayscale(), hue-rotate(), invert(), opacity(), saturate() and sepia()), omitted values are included and compute to their defaults. This can fix two wpt tests [2].

[1] https://drafts.fxtf.org/filter-effects/#supported-filter-functions
[2] /css/filter-effects/parsing/filter-computed.html
/css/filter-effects/parsing/filter-parsing-valid.html

Priority: -- → P3
Assignee: nobody → violet.bugreport
Status: NEW → ASSIGNED

Filters blur(), invert(), etc. can omit argument.

Pushed by violet.bugreport@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/17d1c1e26e31
Accept empty argument for some filters r=emilio
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/16913 for changes under testing/web-platform/tests
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68

We don't mention default values in our docs.

Keywords: dev-doc-needed
You need to log in before you can comment on or make changes to this bug.