- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 11 Feb 2015 14:42:46 +1100
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: Rik Cabanier <cabanier@gmail.com>, "public-fx@w3.org" <public-fx@w3.org>
On Wed, Feb 11, 2015 at 1:54 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 2/10/15 6:13 PM, Tab Atkins Jr. wrote: >> >> Please suggest better wording, but the intent is that the "canvas >> color" defined here is a final underlying layer underneath everything >> else, which solely provides a final compositing step to ensure the >> page is opaque, and is not accessible to any other bit of CSS >> functionality. > > > OK. So it sounds like we need two separate concepts: > > 1) This fallback canvas color that everything is composited on top of. I > agree that this should not be affected by filters. > > 2) The "canvas background", which comes from either the root element or the > <body>. This should possibly be affected by filters on the root element Yup. > (and the <body>? Would really rather not go there). No. If the <body> background gets promoted to the canvas, oh well, no filter on it. No need to extend the crazy behavior further than necessary. ~TJ
Received on Wednesday, 11 February 2015 03:43:34 UTC