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

RESOLVED FIXED in Firefox 68

Status

()

enhancement
P3
normal
RESOLVED FIXED
5 months ago
Last month

People

(Reporter: boris, Assigned: violet.bugreport)

Tracking

(Blocks 1 bug, {dev-doc-needed})

unspecified
mozilla68
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox68 fixed)

Details

()

Attachments

(1 attachment)

Reporter

Description

5 months ago

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

Reporter

Updated

5 months ago
Priority: -- → P3
Assignee

Updated

Last month
Assignee: nobody → violet.bugreport
Status: NEW → ASSIGNED
Assignee

Comment 1

Last month

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

Comment 2

Last month
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

Comment 4

Last month
bugherder
Status: ASSIGNED → RESOLVED
Closed: Last month
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
Upstream PR merged

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.