Skip to content

Fix stale jsxref references surfaced by index-based resolution #37059

Description

@caugner

Summary

An upcoming change to the Rari build system (mdn/rari#715) resolves {{jsxref(...)}} macro arguments against an index of the current Web/JavaScript/Reference/* pages, instead of probing candidate URLs and silently following redirects. References whose target no longer exists — removed JavaScript features, translated or renamed slugs, or malformed arguments — used to be masked as redirected links; with the new resolver they surface as broken links.

This affects ~170 jsxref-sourced broken links across 8 locales.

Fix strategy

  • Removed features (e.g. StopIteration, SIMD, ParallelArray, Object.prototype.watch(), Number.toInteger()): de-link to inline code, mirroring the current en-US pages.
  • Renamed / translated slugs (e.g. Gramatica_lexicaLexical_grammar, Modo_estrictoStrict_mode, SentenciasStatements): point the macro at the canonical en-US sub-path.
  • Malformed arguments (e.g. stray spaces before (), percent-encoded slashes): fix the formatting.
  • Non-Reference guide pages (Closures, Data structures, Equality comparisons): jsxref cannot target these (they live under Web/JavaScript/Guide/), so replace the macro with a normal Markdown link.

Per-locale pull requests

Notes

The en-US {{jsxref("function")}} case is out of scope here and handled separately in mdn/content#44732.

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions