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

Re: [css3] About opacity

From: Brad Kemper <brad.kemper@gmail.com>
Date: Tue, 17 Aug 2010 09:46:06 -0700
Cc: Peter Beverloo <peter@lvp-media.com>, Felipe Nascimento de Moura <felipenmoura@gmail.com>, www-style <www-style@w3.org>
Message-Id: <481B7DF2-365D-4948-A545-11DE00A24D89@gmail.com>
To: Simon Fraser <smfr@me.com>

On Aug 17, 2010, at 9:40 AM, Simon Fraser wrote:

> Children cannot be less opaque than their parents because of the way that opacity is rendered. The element with opacity and all its descendants are rendered into a bitmap first, and that bitmap is then painted with the specified opacity value. This approach is necessary, because otherwise overlapping children would have a different appearance. This is also the reason why opacity < 1 creates stacking context.
> 

Right, but couldn't there be a new property or new component value that would allow that child and of of its children to form a new separate stacking context and separate bitmap that was rendered above the parent, without the parent's opacity affecting it? Or does that cause horrible performance with "look ahead" problems?
Received on Tuesday, 17 August 2010 16:46:52 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:30 GMT