W3C home > Mailing lists > Public > public-houdini@w3.org > August 2015

RE : [css-properties-values-api] Transitions and custom properties

From: François REMY <francois.remy.dev@outlook.com>
Date: Fri, 28 Aug 2015 09:59:49 +0200
Message-ID: <DUB408-EAS221D5CA5052071AC2735675A56E0@phx.gbl>
To: Shane Stephens <shans@google.com>, François REMY <francois.remy.dev@outlook.com>, "public-houdini@w3.org" <public-houdini@w3.org>

PS2: I’m still not happy with the way the interaction between polyfills is dealt by the specification, but I think this is one of the things on the agenda for the meeting, so I’ll wait to see what comes out of the discussions at that time.

	Can you describe what specific concerns you have so we can discuss them?
My opinion on this matter didn’t change since last time I wrote about it. There are already discussions on the matter earlier on this mailing list.

To make a TLDR I don’t want to end up in a world where a polyfill included in an ad-service script can break polyfills already used on the page (or, worse, could do so unpredictibly based on race conditions). That means I want the browser to host a mitigation layer and not rely on people using the same Framework managing this for them, essentially creating conflict issues between two such frameworks.

Best regards,
Received on Friday, 28 August 2015 08:00:26 UTC

This archive was generated by hypermail 2.3.1 : Friday, 28 August 2015 08:00:26 UTC