On Thu, Aug 2, 2012 at 2:42 AM, Robert O'Callahan <robert@ocallahan.org>wrote: > 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(). aha, so it's more like my suggestion: *Maybe you could say that element() can only reference elements that establish a context or elements that don't contain another context.* Since you're establishing a new context, could we make so it would be OK for your ancestor to have a "display:none"?
Received on Thursday, 2 August 2012 16:01:58 UTC