W3C home > Mailing lists > Public > public-fx@w3.org > January to March 2013

Re: [Compositing] Which non-default behaviors create stacking contexts?

From: Rik Cabanier <cabanier@gmail.com>
Date: Wed, 6 Mar 2013 12:32:44 -0800
Message-ID: <CAGN7qDCdkCU3VeALyev_aYUrrLpg6serk2hJHAMnvHKSUUaUhA@mail.gmail.com>
To: "L. David Baron" <dbaron@dbaron.org>
Cc: public-fx@w3.org
mix-blend-mode calls out [1] when it is supposed to happen, but not the
other properties.
mix-composite is the identical to mix-blend-mode. Isolation is basically
about forcing a stacking context.

I will update the spec to make this more clear.

Rik

1:
https://dvcs.w3.org/hg/FXTF/rawfile/default/compositing/index.html#mix-blend-mode


On Tue, Mar 5, 2013 at 11:12 PM, L. David Baron <dbaron@dbaron.org> wrote:

>
> https://dvcs.w3.org/hg/FXTF/rawfile/tip/compositing/index.html#csscompositingrules_CSS
> says:
>
>   # The application of non-default blending or compositing to an
>   # element formatted with the CSS box model must also establishe a
>   # stacking context the same way that CSS β€˜opacity’ does.
>
> This doesn't defined which properties count for "non-default
> blending or compositing".  It needs to do so; the spec basically
> isn't even understandable without knowing which properties this is
> talking about.  (In particular, is it referring to just
> mix-composite and mix-blend-mode, or also to some or all of
> isolation, knock-out, background-composite, or
> background-blend-mode?)
>
> -David
>
> --
> π„ž   L. David Baron                         http://dbaron.org/   𝄂
> 𝄒   Mozilla                           http://www.mozilla.org/   𝄂
>
>
Received on Wednesday, 6 March 2013 20:33:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 6 March 2013 20:33:14 GMT