- From: Max Polk <maxpolk@gmail.com>
- Date: Sun, 02 Feb 2014 09:15:40 -0500
- To: Ric <ric@webplatform.com>, Eliot Graff <Eliot.Graff@microsoft.com>
- CC: "public-webplatform@w3.org" <public-webplatform@w3.org>
On 2/1/2014 7:37 PM, Ric wrote: > Looks great! > > I have a question - I was reviewing the docs import and noticed an object I had not seen before - the DataView. Upon research, I found the browsers I support do not have this defined. > > Are there plans to add/merge a compatibility chart, such as on Mozilla? > https://developer.mozilla.org/en-US/docs/Web/API/DataView For this project we also thought about which ECMAScript version to base the reference documentation upon. So at: http://docs.webplatform.org/wiki/WPD:Projects/javascript We wrote: "The version of JavaScript documented will initially be based on the ECMA-262 edition 5.1 standard of June 2011 <http://www.ecma-international.org/publications/standards/Ecma-262.htm>, since it has the greatest browser conformance <https://en.wikipedia.org/wiki/ECMAScript#Conformance_tests>." It referenced https://en.wikipedia.org/wiki/ECMAScript#Conformance_tests We have a base version upon which www.webplatform.com/javascript is based on. And there exists an ECMAScript conformance test suite to test browsers using that base version. Knowing this, it doesn't seem wise to write our own conformance utilities and tests, based on *whatever pages* people happen to throw into webplatform docs /javascript, but rather, stick with the 5.1 ECMAScript version as planned, and then take advantage of the high-quality completed work of the ECMAScript conformance test suite. Because we commit to a standard version, we can take advantage of the standard version tools that already exist. Permit anything to be thrown into the pot, and you lose that advantage.
Received on Sunday, 2 February 2014 14:16:10 UTC