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

[fxtf-drafts] [filter-effects] <feFuncX> `type` attribute doesn't have a default

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

== [filter-effects] <feFuncX> `type` attribute doesn't have a default ==
There is no initial/default/lacuna value specified for the [`type` attribute](https://drafts.fxtf.org/filters/#element-attrdef-fecomponenttransfer-type) of feFuncR/feFuncG/feFuncB/feFuncA. 

I'm going to guess that browsers use `identity` (and therefore ignore all other attributes if `type` isn't specified) but I haven't tested.


Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/175 using your GitHub account
Received on Thursday, 25 May 2017 02:09:32 UTC

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