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

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

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 20 Sep 2016 01:56:00 -0700
Message-ID: <CAAWBYDCXhz3o_TPdEZHQ4P6jsK_bb9t2gXdYxgZt728_rqsfqA@mail.gmail.com>
To: Andrew Prendergast <ap@vizdynamics.com>
Cc: "public-fx@w3.org" <public-fx@w3.org>
On Wed, Sep 14, 2016 at 10:39 PM, Andrew Prendergast <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:
> https://bugs.chromium.org/p/chromium/issues/detail?id=646993
>
> 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
> matrix3d().

As I've responded to identical threads a few times in the last few
days, I'll just point to my earlier response at
<https://github.com/w3c/svgwg/issues/264#issuecomment-246750601>.

~TJ
Received on Tuesday, 20 September 2016 08:56:51 UTC

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