- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Sun, 05 Jul 2020 21:44:53 +0000
- To: public-fxtf-archive@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. The situation with Firefox (and Webkit most likely) it is just a browser bug that should be fixed. > 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). It's not just size and position. Even filters that don't affect such things would have ill-defined behavior for non-contained elements, and make it significantly more difficult to implement hardware-accelerated rendering paths. -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/11#issuecomment-653942954 using your GitHub account
Received on Sunday, 5 July 2020 21:44:55 UTC