W3C home > Mailing lists > Public > public-fx@w3.org > July to September 2016

Re: [css-transforms] CSS3D breaks with opacity flattening

From: Matt Woodrow <mwoodrow@mozilla.com>
Date: Wed, 21 Sep 2016 20:06:23 +1200
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Rik Cabanier <cabanier@gmail.com>, /#!/JoePea <trusktr@gmail.com>, Chris Harrelson <chrishtr@google.com>, Simon Fraser <simon.fraser@apple.com>, "public-fx@w3.org" <public-fx@w3.org>
Message-ID: <d2fb8db8-6b3c-d7ce-6c93-9a36866c29d7@mozilla.com>

On 21/09/16 7:02 PM, Tab Atkins Jr. wrote:
> On Tue, Sep 20, 2016 at 9:38 PM, Matt Woodrow <mwoodrow@mozilla.com> wrote:
>> This is the core of my point, why should you have to expect it to flatten?
>> I've shown that this isn't actually a requirement, only the convenient way
>> of handling group opacity
> Because otherwise opacity works totally differently in 3d than it does
> in 2d, in a difficult-to-explain way.  translateZ() and z-index should
> work similarly, as they're doing the same thing.
Can you please explain what you mean by this?

If you look at my examples, it's still applying the opacity as a group. 
The difference is that it doesn't flatten preserve-3d, which has no 
analogue in 2d.

- Matt
Received on Wednesday, 21 September 2016 08:06:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:49:57 UTC