Closed
Bug 851411
Opened 11 years ago
Closed 11 years ago
Array page has lost method information
Categories
(Developer Documentation Graveyard :: JavaScript, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: a, Unassigned)
References
Details
I spend a lot of time at the Array page. I've noticed recently documentation has been lost. I've tried to track down where the loss comes from, and am stuck. I suspect a KumaScript parsing error of https://developer.mozilla.org/en-US/docs/JavaScript/Reference/Global_Objects/Array/prototype Details: The page I always visit to look up array methods is: https://developer.mozilla.org/en-US/docs/JavaScript/Reference/Global_Objects/Array It used to list all the array methods as recently as March 1st according to webarchive: http://web.archive.org/web/20130301215415/https://developer.mozilla.org/en-US/docs/JavaScript/Reference/Global_Objects/Array Now it does not. The main page includes the methods using the page macro: {{ page('en-US/docs/JavaScript/Reference/Global_Objects/Array/prototype', 'Properties') }} {{ page('en-US/docs/JavaScript/Reference/Global_Objects/Array/prototype', 'Mutator_methods') }} {{ page('en-US/docs/JavaScript/Reference/Global_Objects/Array/prototype', 'Accessor_methods') }} {{ page('en-US/docs/JavaScript/Reference/Global_Objects/Array/prototype', 'Iteration_methods') }} If you look at the referenced page at: https://developer.mozilla.org/en-US/docs/JavaScript/Reference/Global_Objects/Array/prototype all the methods are still there, with proper div ids. For some reason, the page macro is not including the page properly. https://developer.mozilla.org/en-US/docs/Template:page Instead of including 4 different subsections (Properties, Mutator_methods, Accessor_methods, etc), the Properties section gets included 4 times iin a row. This is a dup #780347, with more detailed information.
Reporter | ||
Comment 1•11 years ago
|
||
Works now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•