W3C home > Mailing lists > Public > www-style@w3.org > May 2013

Re: [css-compositing]new Editor's draft posted

From: Rik Cabanier <cabanier@gmail.com>
Date: Tue, 21 May 2013 20:40:14 -0700
Message-ID: <CAGN7qDCA+MpycQ47g0AG7uQ29vwP118jfw6j-s+jL0E5DkkD+g@mail.gmail.com>
To: public-fx@w3.org, www-style list <www-style@w3.org>, www-svg <www-svg@w3.org>, David Baron <dbaron@dbaron.org>, "Robert O'Callahan" <robert@ocallahan.org>
As a quick recap, people voiced concerns about the following issues before:
- background-blend-mode blends with the entire backdrop of the element
- does mix-blend-mode create a stacking context?
- what is the backdrop of mix-blend-mode?

The spec was changed so:
- images that have background-blend-mode applied will only blend between
themselves and the background color
- mix-blend-mode always creates a stacking context
- the backdrop is the stacking context of your ancestor -> this still needs
more discussion and is marked as an issue since it could be the ancestor

CSS constructs that create groups or layers, is something that developers
are getting more familiar with.
I realize that browser vendors are hesitant to specify them but it looks
that Google is starting to educate its users about them.
For instance, layers (and their effect on performance) are discussed at
Google IO here:



On Mon, May 20, 2013 at 8:42 PM, Rik Cabanier <cabanier@gmail.com> wrote:

> In preparation of the Tokyo face-to-face, I made the compositing spec [1]
> ready for the next working draft.
> I added several examples and did general cleanup.
> During the joint FX day, I would like to discuss the issue of how we can
> determine what the backdrop of an element with blending is.
> Specifically:
> - what CSS constructs create groups that limit the backdrop
> - how can we specify this and in what spec should we do this
> - how can we ensure that this can be implement in a interoperable way.
> 1: https://dvcs.w3.org/hg/FXTF/rawfile/default/compositing/index.html
Received on Wednesday, 22 May 2013 03:40:45 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:11 UTC