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

[fxtf-drafts] filter-effects] drop-shadow can accept color before lengths

From: Eric Willigers via GitHub <sysbot+gh@w3.org>
Date: Thu, 19 Oct 2017 04:37:43 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issues.opened-266718112-1508387862-sysbot+gh@w3.org>
ewilligers has just created a new issue for https://github.com/w3c/fxtf-drafts:

== filter-effects] drop-shadow can accept color before lengths ==
The current spec suggests the color must appear last.
https://drafts.fxtf.org/filter-effects/#funcdef-filter-drop-shadow
drop-shadow() = drop-shadow( <length>{2,3} <color>? )

However, Blink and Firefox accept the color first.

Regardless of the author-supplied order, Blink serializes with the color first, and Firefox serializes with the color last.

"drop-shadow(rgb(4, 5, 6) 1px 2px)" becomes "drop-shadow(1px 2px rgb(4, 5, 6))" in Firefox.
"drop-shadow(1px 2px rgb(4, 5, 6))" becomes "drop-shadow(rgb(4, 5, 6) 1px 2px)" in Blink.

We could change the grammar to
drop-shadow() = drop-shadow( [ <length>{2,3} && <color>? ] )

Test PR that should be updated if this proposal is accepted:
https://github.com/w3c/web-platform-tests/pull/7890


Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/231 using your GitHub account
Received on Thursday, 19 October 2017 04:37:53 UTC

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