- From: Ellie via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Oct 2020 04:11:06 +0000
- To: public-fxtf-archive@w3.org
> And then in that case, the backdrop behind C isn't backdrop-filtered. Is that right? No. The problem is that C's positioning is completely messed up (by spec, because it limits children to the area of a backdrop'ed parent). > I don't know of a great workaround for what you're trying to accomplish, other than making the C elements siblings, instead of children, of B, and apply backdrop-filter to C also. Would that not work? This messes up the markup. You can see this in the code example I coded, I would be forced to move the `<h1>` outside of the `<content>` tag. This really ruins the semantic meaning, therefore I think this backdrop restriction is unreasonable. I absolutely don't care if C is backdrop-filtered or not - in fact, I would expect it not to be as you suggested, if it is outside the area of B. But that is not the problem, the problem is that it isn't even *allowed* to be outside the area of B. -- GitHub Notification of comment by ell1e Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/408#issuecomment-718347404 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 29 October 2020 04:11:08 UTC