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

Re: [css-compositing] why general blending is confusing

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sat, 12 Oct 2013 04:00:10 -0400
Message-ID: <CAOp6jLZO7WuXi7rBacDGOBVpA1J7qSwUzi_ErMxH9BaV39dgDg@mail.gmail.com>
To: Dean Jackson <dino@apple.com>
Cc: www-style list <www-style@w3.org>
On Fri, Oct 11, 2013 at 9:00 PM, Dean Jackson <dino@apple.com> wrote:

> Notice that in 4, the child does NOT blend outside its parents bounds.
> That’s
> because it doesn’t have any background pixels to blend with at that point.
> Sure, the
> translateZ(0) forced a stacking context (compositing layer) on the parent,
> but
> this could have happened for a number of reasons - e.g. a sibling of the
> parent
> having a hover effect that triggered compositing.
> I’m not sure there are any good ways around this without accumulating
> buffers
> (potentially prohibitively expensive), and even then things like animations
> and media will make it harder.

I'm not sure what problem you're pointing to. Are you saying the spec is
unclear, or that it's too hard to implement in some situations (which
situations?), or that it's too complicated for authors to understand, or
something else?

Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w  *
Received on Saturday, 12 October 2013 08:00:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:35 UTC