W3C home > Mailing lists > Public > www-style@w3.org > August 2012

Re: [css4-images] element() behavior

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 2 Aug 2012 21:42:28 +1200
Message-ID: <CAOp6jLYUbNYhDAZ=JhifQHxRJYQ7EjHsNf2dnQENCEUHYmLQ2g@mail.gmail.com>
To: Simon Fraser <smfr@me.com>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Rik Cabanier <cabanier@gmail.com>, www-style list <www-style@w3.org>
On Thu, Aug 2, 2012 at 5:49 AM, Simon Fraser <smfr@me.com> wrote:

> However, I wonder if this doesn't conflict with our earlier decision that
> when you render the element(), it's as if you're starting painting from the
> root, but only painting the target element and its descendants. Things like
> filters etc. will create stacking context. So if the element() target has
> an ancestor with a filter, we paint its positioned descendants in their
> normal painting order (affected by the fact that the filter creates
> stacking context), but we don't actually apply the effect of the filter.

Good point.

What we actually do in Gecko is treat the element target as a stacking
context when rendering its contents for element().

“You have heard that it was said, ‘Love your neighbor and hate your enemy.’
But I tell you, love your enemies and pray for those who persecute you,
that you may be children of your Father in heaven. ... If you love those
who love you, what reward will you get? Are not even the tax collectors
doing that? And if you greet only your own people, what are you doing more
than others?" [Matthew 5:43-47]
Received on Thursday, 2 August 2012 09:42:49 UTC

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