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

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

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 22 May 2013 14:16:56 +0800
Message-ID: <CAOp6jLYhJk3_BXQcp_=Gpuo9fz0yLLmkROi6ecTRGg2soLedPA@mail.gmail.com>
To: Rik Cabanier <cabanier@gmail.com>
Cc: "public-fx@w3.org" <public-fx@w3.org>, www-style list <www-style@w3.org>, www-svg <www-svg@w3.org>, David Baron <dbaron@dbaron.org>
On Wed, May 22, 2013 at 11:40 AM, Rik Cabanier <cabanier@gmail.com> wrote:

> - 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 layer.


I don't see how that helps much. An element's ancestor's stacking context
could contain all kinds of content below the element, which the browser
could have assigned to layers in various ways.

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:
>
> https://developers.google.com/events/io/sessions/325933151
> https://developers.google.com/events/io/sessions/325091862
>
>
I don't think it's a good idea to teach authors to create content optimized
for one specific rendering implementation.

Rob
-- 
q“qIqfq qyqoquq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qyqoquq,q qwqhqaqtq
qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq
qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qtqhqeqmq.q qAqnqdq qiqfq qyqoquq
qdqoq qgqoqoqdq qtqoq qtqhqoqsqeq qwqhqoq qaqrqeq qgqoqoqdq qtqoq qyqoquq,q
qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq
qsqiqnqnqeqrqsq qdqoq qtqhqaqtq.q"
Received on Wednesday, 22 May 2013 06:17:28 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 22 May 2013 06:17:28 UTC