- From: Robin Berjon <robin@w3.org>
- Date: Thu, 04 Jul 2013 11:47:25 +0200
- To: Tobie Langel <tobie@w3.org>
- CC: Marcos Caceres <w3c@marcosc.com>, François REMY <francois.remy.dev@outlook.com>, Brian Kardell <bkardell@gmail.com>, public-nextweb@w3.org
On 04/07/2013 11:31 , Tobie Langel wrote: > To summarize, specs are going to seriously change between what is > prollyfilled ([insert snarky comment here]) and what gets shipped, > and that's going to cause plenty of grief down the road. To mitigate > this solid test suites using testharness.js would help along with a > system to easily identify native code from prolyfills. Test suites are useful, but they're not going to solve the issues you described with Prototype. I would say, to mitigate this, only shim things when there are shipping implementations and some modicum of stability as to how they behave, so as to bring the functionality to older implementations (or paper over bugs). Before that, it's best to show the value of the behaviour by exposing it in a completely different — and safe — context. -- Robin Berjon - http://berjon.com/ - @robinberjon
Received on Thursday, 4 July 2013 09:47:36 UTC