Cannot display other `<input>` types on sidebars at some localized page
See original GitHub issueSummary
When going through localization work under HTML “<input>
types”, I found it hard to navigate between different pages of <input>
type, and for other languages’ page(en-US/zh-TW/ja/fr/es), however, can correctly display related <input>
type page on sidebar.
URL
- https://developer.mozilla.org/zh-CN/docs/Web/HTML/Element/Input
- https://developer.mozilla.org/ko/docs/Web/HTML/Element/Input
- https://developer.mozilla.org/ru/docs/Web/HTML/Element/Input
Reproduction steps
- Go to any of the URL listed in URL section.
- Only ‘HTML Elements’ is displayed on the ‘Related Topics’ section.
Expected behavior
“<input>
types” and any other elements related also display on the ‘Related Topics’ section like the English version
Actual behavior
“<input>
types” does not display
Device
Desktop
Browser
Edge
Browser version
Stable
Operating system
Windows
Screenshot
here is what all localization page should be:
zh-CN page is not displaying “<input>
types” section, some other elements are not displaying either.
ko page is not displaying the “<input>
types” section
ru page is not displaying the “<input>
types” section, and some elements are missing
Anything else?
No response
Validations
- I have read the Community Participation Guidelines.
- I have verified that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
- I have checked that this is a concrete bug. For Q&A open a GitHub Discussion.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Localizing help center content - Zendesk help
The help center displays pages in different languages based on locale code in the page URL. Example, ".../hc/en-us".
Read more >Manual talk:Interface/Sidebar - MediaWiki
I propose we rename this page to 'Manual:Sidebar'. 'Sidebar' seems to be the name the developers have chosen for this part of the...
Read more >VSCode showing "cannot find module" TS error for .vue import ...
In the Sidebar.vue file, try to add the ".vue" extension in import ... Type built and select "Extensions: Show Built-in Extensions".
Read more >Setting Up Language-Specific Definitions in Service Edge UI
In the sidebar menu, select Configuration > General Settings, and select the Localization page. Select the option to Allow Multiple Languages Localization.
Read more >Switching the localization language in AG Grid
In this blog I'll be showing how to switch the localization language on the fly in AG Grid to easily support users for...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After we have replaced the {{HTMLRef}} macro in translated-content. It’s no more an issue.
@caugner / @wbamberg
tags
should be inferred from the English “reference” document (see https://github.com/mdn/translated-content/issues/7412) In other words “the set of tags of a localized page should at least contain the tags of the English page”IMO, both Yari and KS macros should obey the same logic while resolving metadata. (see https://github.com/mdn/yari/blob/main/kumascript/index.ts#L56-L69 )
I guess a fix for the
HTMLRef
macro could be a palliative or we could directly go forward in localized docs and useHTMLSidebar
@jasonren0403 would the second option solve the issue for you?