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: Sat, 04 Jul 2020 02:30:37 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-653710280-1593829836-sysbot+gh@w3.org>
The spec need to make exception for filters that have nothing to do with size or positioning (color-based filters for example).

If I want to grayscale the entire page, why should that have any effect on absolute/fixed positioned descendants?

Take a look at this example:
https://stackoverflow.com/questions/62717289/

There, I'm trying to grayscale an entire webpage that contains a fixed positioned element. As soon as I apply the filter, it breaks the positioning (no longer allowing me to fix that element to the "Dead Center" of the page).

Shouldn't the type of filter be taking into consideration instead just assuming that all filters must sabotage fixed/absolute positioning? If a particular filter has nothing to do with size/positioning, then no descendants should be encapsulated with a container-elements.

I'm very disappointed that the spec doesn't provide any granularity: all filters corrupt fix/absolute descendants, while that behavior should only be reserved for those certain filter-types that really can't work without that treatment.

A filter that only effects color, shouldn't bother descendant's position in any way!

-- 
GitHub Notification of comment by Lonniebiz
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/11#issuecomment-653710280 using your GitHub account
Received on Saturday, 4 July 2020 02:30:38 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 4 July 2020 02:30:39 UTC