- From: Andrew Prendergast <ap@vizdynamics.com>
- Date: Thu, 15 Sep 2016 05:39:53 +0000
- To: "public-fx@w3.org" <public-fx@w3.org>
- Message-ID: <E119A6ACA1E659419D330C8CBF8B6B7698780555@EX2K10MBX08.secure.hosting>
Dear fellow CSS-ers, 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(). Regards, ap Andrew Prendergast Chief Scientist VizDynamics M +61 409 941 901 | skype ap.vizdynamics | ap@vizdynamics.com<mailto:ap@vizdynamics.com> | www.vizdynamics.com<http://www.vizdynamics.com/> APAC Support | +61 1300 858 428 | Level 39, 385 Bourke Street | Melbourne VIC 3000 USA Support | +1 650 251 4288 | 228 Hamilton Av, 3rd Floor | Palo Alto CA 94301 Meet Data, your new team member @ blog.vizdynamics.com<http://blog.vizdynamics.com/>
Received on Friday, 16 September 2016 13:54:04 UTC