W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > June 2017

Re: [fxtf-drafts] [filter-effects] Make grayscale() work without parameters

From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
Date: Sun, 11 Jun 2017 06:00:23 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-307608828-1497160822-sysbot+gh@w3.org>
@AmeliaBR The spec _does_ say initial value for interpolation.

I did. run some testing in Safari and Chrome. Both support value-less filter functions for all functions but `drop-shadow()`:
* `blur()`: `blur(0)` **no effect**
* `brightness()`: `brightness(0)`
* `contrast()`: `contrast(1)` **no effect**
* `drop-shadow()`: **not supported**
* `grayscale()`: `grayscale(1)`
* `hue-rotate()`: `hue-rotate(0)` **no effect**
* `invert()`: `invert(1)`
* `opacity()`: `opacity(1)` **no effect**
* `sepia()`: `sepia(1)`
* `saturate()`: `saturate(1)` **no effect**

Firefox follows the spec still.

`saturate()`, `contrast` don't seem to follow the general default values but IMO make sense. There is no clear "opposite".

IMO most values do make sense. I don't think that `brightness(0)` as default is useful since it simply turns elements to black. I rather would align them with `saturate()`, `contrast`.

@grorg @smfr Do you remember the thoughts that went into the default behavior?

GitHub Notification of comment by dirkschulze
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/1#issuecomment-307608828 using your GitHub account
Received on Sunday, 11 June 2017 06:00:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 November 2018 00:45:58 UTC