W3C home > Mailing lists > Public > public-fx@w3.org > April to June 2011

Re: Updated filters specification

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 27 Apr 2011 15:55:36 +1200
Message-ID: <BANLkTimp2TW0w6wO+XStTAmBY6eq6ngsMQ@mail.gmail.com>
To: Erik Dahlstrom <ed@opera.com>
Cc: Rik Cabanier <cabanier@gmail.com>, Dean Jackson <dino@apple.com>, Dirk Schulze <vbs85@gmx.de>, public-fx@w3.org, Anthony Grasso <anthony.grasso@cisra.canon.com.au>
On Tue, Apr 26, 2011 at 7:20 PM, Erik Dahlstrom <ed@opera.com> wrote:

> Deprecating (or dropping) 'enable-background' would essentially mean that
> BackgroundImage and BackgroundAlpha would always generate a transparent
> black result in the context of filters (I presume this is what the browsers
> that don't support enable-background already do, and it follows the error
> handling that is defined for when there was no "enable-background:new"
> parent element). Typically that means that things still render without
> errors but probably not as intended by the author.


Why can't we define BackgroundImage and BackgroundAlpha in a way that
continues to work in the absence of enable-background? I think we can, even
with GPU-accelerated rendering. In the worst case you can detect use of
BackgroundImage/BackgroundAlpha and automatically infer the equivalent of
enable-background for the ancestor elements.

Rob
-- 
"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
Received on Wednesday, 27 April 2011 03:56:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 April 2011 03:56:05 GMT