W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > July 2020

Re: [fxtf-drafts] filter should be defined to establish a containing block for fixed and absolutely positioned elements (#11)

From: Lonnie Best via GitHub <sysbot+gh@w3.org>
Date: Sun, 05 Jul 2020 15:01:20 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-653899449-1593961279-sysbot+gh@w3.org>
@chrishtr Those containing blocks do indeed break fixed/absolute positioned descendants and the root element exception that's working in Chromium, and [not in Firefox](https://bugzilla.mozilla.org/show_bug.cgi?id=1650522), is not enough in my opinion.

On filters that modify color, and have no aspiration of modifying size or position, the containing blocks should not be created even if the target element is NOT root. I've submitted a separate issue [here](https://github.com/w3c/fxtf-drafts/issues/402). The spec should impose the granularity of making the containing blocks conditional based on the type(s) of filters being applied and not just the non-granular all filters approach. Color related filters like `grayscale` and `invert` should not invoke the creation of containing blocks (even when applied to non-root elements).

For example, `body { filter: grayscale(100%); }`, should not cause the creation of containing blocks, even though the filter is being placed on `body` instead of `:root`. This should be the case on any element. https://github.com/w3c/fxtf-drafts/issues/402

-- 
GitHub Notification of comment by Lonniebiz
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/11#issuecomment-653899449 using your GitHub account
Received on Sunday, 5 July 2020 15:01:22 UTC

This archive was generated by hypermail 2.4.0 : Sunday, 5 July 2020 15:01:23 UTC