Skip to content

Links text and buttons UI are Overlapping with Zoom 200%, 400%, Text Scaling & High Dpi #1853

Closed

Description

@msftedad

Environment Details

OS version: Windows11 version 21H2 (OS build 22000.856)
Edge version: 104.0.1293.47

Repro Steps:

  1. Open URL: Document (1).mhtml
  2. Apply text size to 200% and resolution 1280x720.
  3. And observe that "my heading is a list item" and "example" texts are getting to overlap

Actual Result:

After resizing and reflowing text is getting to overlap

Expected Result:

After resizing and reflowing text should not get overlapped

Screenshot Attachment:

image

Activity

  1. trusktr commented on Aug 13, 2022

    @trusktr
    Member

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

  2. msftedad commented on Aug 17, 2022

    @msftedad
    Author

    Hi Team,

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

  3. trusktr commented on Aug 20, 2022

    @trusktr
    Member

    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?

  4. msftedad commented on Sep 1, 2022

    @msftedad
    Author

    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.

  5. v-sudmandal commented on Sep 19, 2022

    @v-sudmandal

    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.

  6. SritejaGolla commented on Sep 26, 2022

    @SritejaGolla

    Hi @trusktr

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

  7. v-sudmandal commented on Oct 7, 2022

    @v-sudmandal

    Hi @trusktr

    Any update on the above bug?

  8. v-shamohsin commented on Jan 4, 2023

    @v-shamohsin

    Hello @trusktr

    Can you provide an update on this please

  9. v-shamohsin commented on Jan 18, 2023

    @v-shamohsin

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

  10. v-shamohsin commented on Jan 27, 2023

    @v-shamohsin

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

  11. msftedad commented on Apr 21, 2023

    @msftedad
    Author

    Hi Team, is there any update on this bug?

  12. msftedad commented on Jan 12, 2024

    @msftedad
    Author

    Hi Team, Is there any update on this issue?

  13. msftedad commented on Mar 7, 2024

    @msftedad
    Author

    Hi Team, Is there any update on this issue?

  14. modified the milestones: 6.x, 5.x on Jun 16, 2024
  15. linked a pull request that will close this issuefeat: v5 style overhaul #2469on Jul 19, 2024
  16. jhildenbiddle commented on Jul 19, 2024

    @jhildenbiddle
    Member

    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.

  17. msftedad commented on Jul 22, 2024

    @msftedad
    Author

    Thanks for the update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions