Re: [w3ctag/design-reviews] Backdrop Filter (#353)

Just to add a bit more color to this discussion - if you read through the [w3c/fxtf-drafts#53](https://github.com/w3c/fxtf-drafts/issues/53) discussion, you'll see a rather large conversation about the fundamental problems with nesting backdrop-filter inside filter/opacity parents. Our proposed/approved spec addresses this issue by defining the [Backdrop Root](https://drafts.fxtf.org/filter-effects-2/#BackdropRoot) concept, which avoids these issues while allowing **as much** of Webkit's shipped (but unspec'd) implementation as possible. We iterated the spec multiple times with comments and discussion from the community, and we were able to remove many (but not all) of the restrictions on backdrop-filter. There is also a large discussion within the spec relating to these issues, and describing why the Backdrop Root is necessary. This issue was discussed at length, both in the github issue, as well as at the Feb 25 F2F, and both Edge and Mozilla gave supporting comments both places. Webkit's objection at the F2F, which is the sole reason for the note about a lack of consensus, is that backdrop filter should "just filter everything". There has been an open action item for Webkit to resolve/address the [fundamental problems](https://github.com/w3c/fxtf-drafts/issues/53#issuecomment-451599226) with that proposal since Oct 2018.

I do apologize for not including a more detailed state of implementation among the browsers.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/353#issuecomment-495932080