W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > May 2018

Re: [fxtf-drafts] [filter-effects-1] What is the visual effect of filter() on the document element?

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Wed, 30 May 2018 21:06:27 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-393319374-1527714386-sysbot+gh@w3.org>
Again, these sorts of polls aren't particularly useful. This isn't something people have thought about before, so you're just getting a kneejerk response, and the phrasing of the question ("turn the default white background black") misleads the intuition, too - it *sounds* like you're saying the <html> element has a white background by default, and so the two code examples are equivalent (just that the first omits a background and so gets the default white), when actually the two examples give the <html> element totally different background declarations.

Sure, getting people's quick intuitions can be useful, but those intuitions can also be *inconsistent*, and it's better for everyone to have a consistent, rational platform even if occasionally corner cases require an "oh, I get it" moment.

If *nothing else*, changing it to ask about `background: transparent` vs `background: white` would at least make the distinction a little clearer and put people in the right mind to think about it, particularly if you also ask to contrast with a `div` with those same declarations.  (The distinction between the element's background and its backdrop isn't always at the top of a person's mind, and the confusing interplay between those two and the "html/body promote their backgrounds to the canvas background" feature just makes it worse.)

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/282#issuecomment-393319374 using your GitHub account
Received on Wednesday, 30 May 2018 21:06:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:23 UTC