Hello! The link is not working. It takes me to a Microsoft login page.

Hi Team,

Here is the open URL to reproduce the issue https://zorana-jankovic.github.io/example/#/

It is like trying to render desktop content on mobile if you zoom in like that. Why do you need to zoom like that? What do you think the solution should be?

Hi,

This is the common way low vision users can see the content without confusion.

According to the https://www.w3.org/WAI/WCAG21/Understanding/resize-text and https://www.w3.org/WAI/WCAG21/Understanding/reflow WCAG rules the content should not get overlapped.

Hi @msftedad

Please let us know your plans on fixing this bug so that our team will regress and close it which makes the product compliant.

Hi @trusktr

Any update on the above bug ? Please let us know your plans on fixing this bug.

Hi @trusktr

Any update on the above bug?

Hello @trusktr

Can you provide an update on this please

Hi @trusktr , Can you please provide an update on this please. Thanks

Hi @trusktr , Can you please provide an ETA for the fix

Hi Team, is there any update on this bug?

Hi Team, Is there any update on this issue?

Hello @msftedad --

This issue will not be completely resolved by PR #2469 but it will (hopefully) be a little easier to deal with. The changes will be available when Docsify v5 is released.

Once v5 is release, the navbar height can be adjusted easily using the following CSS custom property:

:root {
  --navbar-height: 4em;
}

That said, stuffing a large number of elements into a horizontal navbar is going to be problematic regardless of the --navbar-height setting. I believe the intent of the original design (which was before my time) was to have either a limited number of root-level navbar items or to leverage drop-down menus in the when needed (as was done with the "Translations" menu on https://docsify.js.org):

- Translations

  - [:uk: English](/)
  - [:cn: 简体中文](/zh-cn/)
  - [:de: Deutsch](/de-de/)
  - [:es: Español](/es/)
  - [:ru: Русский](/ru-ru/)

There are several ways we could resolve the issue you've described, but each one has trade-offs. We may consider some of these options in a future redesign, but for now it is unlikely that we will change the navbar style/behavior to "fix" the issue as described here because there are alternative approaches that avoid the issue.

Thanks for the update.