1168102 - Add ES1, ES3 to Spec2 and SpecName templates

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: General, defect)

Description

[John Whitlock [:jwhitlock]]

What feature should be changed? Please provide the URL of the feature if possible.
==================================================================================
Two early versions of ECMAScript are not fully represented in the Spec2 and SpecName templates.  MDN pages refer to these specs, such as the documentation for this[1] and the function expression [2].  Possible Spec2 and SpecName data:

ECMAScript 1st Edition.
Key: ES1
Maturity: Standard
Name: ECMAScript 1st Edition (ECMA-262)
URL: http://www.ecma-international.org/publications/files/ECMA-ST-ARCH/ECMA-262,%201st%20edition,%20June%201997.pdf
Spec2: No change
SpecName: Add ES1 entry

ECMAScript 3rd Editiom
Key: ES3
Maturity: Standard
Name: ECMAScript 3rd Edition (ECMA-262)
URL: http://www.ecma-international.org/publications/files/ECMA-ST-ARCH/ECMA-262,%203rd%20edition,%20December%201999.pdf
Spec2: Add ES3 entry
SpecName: Add ES3 entry

[1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/this#Specifications
[2] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/function#Specifications


What problems would this solve?
===============================
KumaScript can't be used to localize these names and statuses.  Users can't click to see the historical specifications.  They are requiring additional work to import in the compatibility data project (bug 1132677).

Who would use this?
===================
MDN contributors would switch to the standard Spec2 and SpecName templates when documenting Javascript.

What would users see?
=====================
ES1 and ES3 specifications would be consistent with other specifications.

What would users do? What would happen as a result?
===================================================
Users could click through, view the PDFs, and be sad that ECMAScript doesn't publish HTML versions.

Is there anything else we should know?
======================================
bug 1132677 can work around this issue, so no dependency is being set.

Comment 1

[John Whitlock [:jwhitlock]]

Fixed by fscholz way back in June 2015:

https://developer.mozilla.org/en-US/docs/Template:SpecName$revision/810897