Closed
Bug 1455134
Opened 8 years ago
Closed 8 years ago
Deprecated Harmony() macro links to untranslated section in Russian
Categories
(Developer Documentation Graveyard :: Macros/Templates, enhancement, P5)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: serg.romankov, Unassigned)
Details
(Whiteboard: [specification][type:bug])
What did you do?
================
1. https://developer.mozilla.org/ru/docs/Web/JavaScript/Reference/Functions/Default_parameters
2. https://developer.mozilla.org/ru/docs/Web/JavaScript/Reference/Functions/Default_parameters#Browser_compatibility
3.
What happened?
==============
click by link and not redirect
What should have happened?
==========================
should redirect to compatibility table
Is there anything else we should know?
======================================
Comment 1•8 years ago
|
||
The link is created by the Harmony KumaScript macro, and uses the English anchor for the Browser Compatibility section:
https://github.com/mdn/kumascript/blob/master/macros/Harmony.ejs#L14
The French version includes a translated anchor.
Component: Wiki pages → Macros/Templates
Product: developer.mozilla.org → Developer Documentation
Summary: Link don't work → Harmony() macro links to untranslated section in Russian
Comment 2•8 years ago
|
||
The harmony macro is obsolete. 355 pages are still using it but shouldn't.
https://developer.mozilla.org/en-US/search?locale=*&kumascript_macros=Harmony&topic=none
CC'ing Sphinx in case he is interested in working on removal.
Updated•8 years ago
|
Summary: Harmony() macro links to untranslated section in Russian → Deprecated Harmony() macro links to untranslated section in Russian
Updated•8 years ago
|
Priority: -- → P5
Since 1456165 has been fixed, I'll work on this in the coming days.
for the record https://github.com/mdn/kumascript/pull/699
PR has been merged, closing this one.
Note: There might a few days of delay for this deletion to be actually in production.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•