Re: [fxtf-drafts] Fix the backdrop-filter order of operations to get opacity right (#361)

I still prefer the approach where the element rendering and the filtered backdrop are part of the same opacity group. My justification at this point is mostly Safari compat. Arguing via intuition / what feels right doesn't seem fruitful because there seem to be at least two different intuitions and we don't know which one is shared by the majority of authors, or if there even is such a thing as a shared intuition among authors about this behavior.

Actually, scratch that, I will try to justify my intuition one more time: I expect fractional opacity values to interpolate between the rendering at opacity:0 and the rendering at opacity:1. If the element foreground is opaque, the filtered backdrop isn't visible at either 0 or 1. So as I modulate my opacity value between those two extremes, I don't expect the filtered backdrop to become partially visible for in-between values.
Furthermore, setting opacity on a given DOM element has always acted as opacity on a single "effect node". The only case that I'm aware of where opacity on a single DOM element operates on multiple effect nodes independently is preserve-3d rendering where opacity gets propagated into the leaf layers. But I think that particular behavior is regarded as an unfortunate exception that was the lesser of two evils.

-- 
GitHub Notification of comment by mstange
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/pull/361#issuecomment-520249871 using your GitHub account

Received on Sunday, 11 August 2019 18:28:27 UTC