mozilla

Revision 129738 of Sevenspade (:crussell)

  • Revision slug: User:Sevenspade
  • Revision title: Sevenspade (:crussell)
  • Revision id: 129738
  • Created:
  • Creator: Sevenspade
  • Is current revision? No
  • Comment todo

Revision Content

I will be mostly (probably exclusively) working on the JavaScript Reference pages.

TODO

Implementation history

Currently, most pages in the JavaScript Reference have a table documenting that particular object/method/property's existence throughout each version of JavaScript. These usually look something like this:

Method of Object
Implemented in: JavaScript 1.x, NES x.0 , JScript ''x''.''x''
ECMA Version: ECMA-262

I plan to work on fully documenting the implementation history and backwards compatibility of each aspect of JavaScript. Changes in behavior for different versions should be noted (particularly JavaScript 1.2). The ECMA specification line is pretty unhelpful because it does not include the revision number for the specification, leaving articles to contain only "ECMA-262," the only ECMAScript specification document (as of now). This should be remedied by adding information about changes to the spec in each revision.

Additionally, should we keep information about Netscape Enterprise Server? Should we include information about implementation in JScript? If so, do we then include information about implementation in Opera? KJS/JavaScriptCore? Currently, there is little-to-no mention of specific browser versions in the Reference, instead referring to everything in the abstract "JavaScript 1.x" way. I think this reference should strive to remain fairly browser neutral, and that the best way to do that would be to continue referring to everything strictly as JavaScript, even if it is a bit Mozilla-biased.

Revision Source

<p>I will be mostly (probably exclusively) working on the <a href="en/Core_JavaScript_1.5_Reference">JavaScript Reference</a> pages.
</p>
<h3 name="TODO"> TODO </h3>
<h4 name="Implementation_history"> Implementation history </h4>
<p>Currently, most pages in the JavaScript Reference have a table documenting that particular object/method/property's existence throughout each version of JavaScript. These usually look something like this:
</p>
<blockquote>

<table class="fullwidth-table">
<tbody><tr>
<td class="header" colspan="2">Method of <a href="en/Core_JavaScript_1.5_Reference/Objects/Object">Object</a></td>
</tr>
<tr>
<td>Implemented in:</td>
<td>JavaScript 1.<i>x</i>, NES <i>x</i>.0 <span class="comment">, JScript ''x''.''x''</span></td>
</tr>
<tr>
<td>ECMA Version:</td>
<td>ECMA-262</td>
</tr>
</tbody></table>
</blockquote>
<p>I plan to work on fully documenting the implementation history and backwards compatibility of each aspect of JavaScript. Changes in behavior for different versions should be noted (particularly JavaScript 1.2). The ECMA specification line is pretty unhelpful because it does not include the revision number for the specification, leaving articles to contain only "ECMA-262," the only ECMAScript specification document (as of now). This should be remedied by adding information about changes to the spec in each revision.
</p><p>Additionally, should we keep information about Netscape Enterprise Server? Should we include information about implementation in JScript? If so, do we then include information about implementation in Opera? KJS/JavaScriptCore? Currently, there is little-to-no mention of specific browser versions in the Reference, instead referring to everything in the abstract "JavaScript 1.<i>x</i>" way. I think this reference should strive to remain fairly browser neutral, and that the best way to do that would be to continue referring to everything strictly as JavaScript, even if it is a bit Mozilla-biased.
</p>
Revert to this revision