New issue
Advanced search Search tips

Issue 618960 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Compat



Sign in to add a comment

Use counter filter functions with no arguments

Project Member Reported by f...@opera.com, Jun 10 2016

Issue description

The Filter Effects spec [1] currently allow some filter functions to have no arguments (i.e essentially default argument values). This is currently supported by Blink, but not Gecko or Edge. There's also some controversy as to what the default argument values should be [2], and what Blink implements currently differ from the spec in some cases.
Aligning with Gecko and Edge would mean a valid -> invalid transition, so content would be (visually) broken. We should add a use counter to gauge the impact before moving in either direction.

[1] https://drafts.fxtf.org/filters/#FilterProperty
[2] https://github.com/w3c/fxtf-drafts/issues/1
 

Comment 1 by f...@opera.com, Jun 10 2016

Status: Assigned (was: Untriaged)

Comment 2 by f...@opera.com, Jun 10 2016

Hmm, actually re-reading the syntax definitions it doesn't look like the spec allows "no arguments" (the grouping used in some places is a bit confusing though.)

Comment 4 by f...@opera.com, Jun 11 2016

Status: Fixed (was: Assigned)

Comment 6 by suzyh@chromium.org, Apr 5 2017

Components: -Blink>CSS>Filters Blink>Compositing>Filters

Sign in to add a comment