Closed
Bug 562402
Opened 15 years ago
Closed 14 years ago
[404] The "XUL Coding Style Guidelines" link near the bottom of https://developer.mozilla.org/en/Introduction_to_XUL
Categories
(Developer Documentation Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: stephen.contact, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.3a5pre) Gecko/20100427 Minefield/3.7a5pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.3a5pre) Gecko/20100427 Minefield/3.7a5pre
The link to "XUL Coding Style Guidelines" in the last paragraph on the https://developer.mozilla.org/en/Introduction_to_XUL page brings up a 404.
Reproducible: Always
Steps to Reproduce:
1. Go to https://developer.mozilla.org/en/Introduction_to_XUL
2. Click the "XUL Coding Style Guidelines" link in the last paragraph
3. http://www.mozilla.org/projects/l10n/xul-styleguide.html is 404
Actual Results:
http://www.mozilla.org/projects/l10n/xul-styleguide.html is 404
Expected Results:
The XUL Coding Style Guidelines document
Reporter | ||
Comment 1•15 years ago
|
||
I think this is where it should be going:
https://developer.mozilla.org/en/XUL_Coding_Style_Guidelines
So...
<a class="external" rel="external nofollow"
href="https://developer.mozilla.org/en/XUL_Coding_Style_Guidelines"
title="https://developer.mozilla.org/en/XUL_Coding_Style_Guidelines"
target="_blank">XUL Coding Style Guidelines</a>
Updated•15 years ago
|
Component: www.mozilla.org → Documentation Requests
Product: Websites → Mozilla Developer Center
QA Contact: www-mozilla-org → doc-request
Comment 2•14 years ago
|
||
Fixed.
A devmo contributor updated this link lately.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Component: Documentation Requests → Documentation
Updated•12 years ago
|
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
You need to log in
before you can comment on or make changes to this bug.
Description
•