Closed
Bug 1244121
Opened 9 years ago
Closed 9 years ago
Long lists of empty bullet points in Plugin API reference
Categories
(Developer Documentation Graveyard :: Add-ons, defect, P5)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: foolip, Unassigned)
References
()
Details
:: Developer Documentation Request
Request Type: Correction
Gecko Version: unspecified
Technical Contact: annevk@annevk.nl
:: Details
The HTML spec references https://developer.mozilla.org/en-US/docs/Plugins/Guide, but since the link was added, the page has changed and broken.
Right after the "Plug-in Side Plug-in API" there is a long list of empty bullet points, and also later. This seems to be because the macro/method Npapi and possibly others doesn't work, but I can't figure out where that's defined.
Context: https://github.com/whatwg/html/issues/573
Comment 1•9 years ago
|
||
nsapi is defined at https://developer.mozilla.org/en-US/docs/Template:npapi, and hasn't changed in a few years. It is used on a few other pages, which also output blank strings when force-refreshed.
Comment 2•9 years ago
|
||
I've made a stop-gap fix that works on this page.
I need to revisit it to make it work on translated pages and also to understand why it suddenly broke. Keeping this open so that I have it on my radar.
Reporter | ||
Comment 3•9 years ago
|
||
Thanks, that fixes the first broken list. Unfortunately, there are two more in the "Scripting plugins" section that are still empty bullets.
Comment 4•9 years ago
|
||
Arrrrg. 2 macros for the same behaviour. Temp-fixed too. Sorry not to have catched up.
(Just when my train is getting on the platform :-) )
Reporter | ||
Comment 5•9 years ago
|
||
Thanks for fixing this!
Comment 6•9 years ago
|
||
Seems like it must be a behavior change related to redirects to me.
Comment 7•9 years ago
|
||
{{xref}} assume that urls have /docs/ in their slug. Which is not the case with zones.
I now fixed the macros for l10n too.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•