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

Re: [css-transforms] CSS3D issue with opacity in Chrome 53

From: Andrew Prendergast <ap@vizdynamics.com>
Date: Sat, 24 Sep 2016 23:15:53 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>
CC: "public-fx@w3.org" <public-fx@w3.org>
Message-ID: <98D854DE-9BFB-4CCB-AE1E-DB298A459A1E@vizdynamics.com>
Hi TJ,

Thanks for the note.

I looked over the various threads myself and I think the core issue is best summarised as follows:

Setting opacity is causing the side effect of modifying the transformation of child nodes and is highly unexpected.

Those working with SVG and CSS3D have provided detailed examples of why this is a problem.

The fix is straightforward - setting opacity should only affect opacity.


On 20 Sep 2016, at 6:56 PM, Tab Atkins Jr. <jackalmage@gmail.com<mailto:jackalmage@gmail.com>> wrote:

On Wed, Sep 14, 2016 at 10:39 PM, Andrew Prendergast <ap@vizdynamics.com<mailto:ap@vizdynamics.com>> wrote:
I am maintaining the repo at http://github.org/aprender/refamous and would
like to add my +1 on the issues caused by the recent opacity “feature”
creeping into Chrome 53 based on the W3C spec.

There is a link to more info here:

I believe that the W3C spec on the matter in question is functionally
incorrect and propose it be amended for two reasons:

-        Philosophically, the scene graph model taught in 3D programming
courses around the world simply will not work with these sort of unintended
side-effects being introduced.
-        From an application perspective, this issue effectively causes one
to add logic to disable use of transparency if one goes anywhere near a

As I've responded to identical threads a few times in the last few
days, I'll just point to my earlier response at

Received on Saturday, 24 September 2016 23:16:35 UTC

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