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

[fxtf-drafts] [filter-effects] Why can't opacity() filter function every increase opacity

From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
Date: Thu, 25 May 2017 17:04:43 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issues.opened-231399173-1495731882-sysbot+gh@w3.org>
AmeliaBR has just created a new issue for https://github.com/w3c/fxtf-drafts:

== [filter-effects] Why can't opacity() filter function every increase opacity ==
The description of [the shorthand `opacity()` filter function](https://drafts.fxtf.org/filters/#funcdef-filter-opacity) says:

>  Values of amount over 100% are allowed but UAs must clamp the values to 1.

Was there a practical reason why the function cannot be used to increase opacity?  Have browsers implemented the clamping of the input parameter?  Or do they only clamp the final value?  (Sorry, don't have time to test right now...)

I think it removes much of the usefulness of the function that it can't be used to increase opacity of semi-transparent regions (e.g., of blurred edges created by `blur()` or `drop-shadow()` ).

Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/178 using your GitHub account
Received on Thursday, 25 May 2017 17:04:50 UTC

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