question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot display other `<input>` types on sidebars at some localized page

See original GitHub issue

Summary

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

  1. https://developer.mozilla.org/zh-CN/docs/Web/HTML/Element/Input
  2. https://developer.mozilla.org/ko/docs/Web/HTML/Element/Input
  3. https://developer.mozilla.org/ru/docs/Web/HTML/Element/Input

Reproduction steps

  1. Go to any of the URL listed in URL section.
  2. 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: should be

zh-CN page is not displaying “<input> types” section, some other elements are not displaying either. current zh-cn

ko page is not displaying the “<input> types” section current ko

ru page is not displaying the “<input> types” section, and some elements are missing current ru

Anything else?

No response

Validations

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:8 (6 by maintainers)

github_iconTop GitHub Comments

2reactions
yin1999commented, Nov 3, 2022

It seems that we are deprecating this macro.

After we have replaced the {{HTMLRef}} macro in translated-content. It’s no more an issue.

image

2reactions
SphinxKnightcommented, Oct 27, 2022

@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 use HTMLSidebar @jasonren0403 would the second option solve the issue for you?

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found