In a small Edge Window, content is cut off and there's no scroll-bar

Confirmed Issue #14375647


Tobi R.
Oct 25, 2017
This issue is public.
Found in
  • Microsoft Edge
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

When I resize Edge to a small width, the page content is cut off (see the cut-off title “Demos” at the top of the page), and the scroll-bar disappears.

Here’s a screenshot:

In Chrome, the title is not cut off and the scroll-bar is present:


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Steven K.”

  • Hi,

    How can I re-run the same test?  Can these tests be shared if I create an account?

    Also, can you send a repro for this?  I would like to run the tests on a development build.

    Appreciate the support,

    The MS Edge Team

  • Hi Steven, hi Edge Team

    The URL of the page is on the linked screenshot page:

    You can try to reproduce the two reported issues by opening
    in Edge (eg on a development build) and resizing the Edge window to be as narrow as possible.

    And if you want to do the exact same test I did, also see the linked screenshot page:
    You’d log into your (existing or new) CrossBrowserTesting account, then at
    start the test specified on the page I linked. From that linked page:
    Open the page on Windows 10 in Microsoft Edge 16 with resolution 1366x768 .
    Then, as described above in my bug report, resize Edge to a small width (eg try the smallest possible width).

    Thanks for investigating the two issues,

  • Microsoft Edge Team

    Changed Assigned To from “Steven K.” to “John J.”

    Changed Assigned To to “Bruce M.”

  • Here’s another test case:

    The page

    in Firefox, Chrome, and in Edge (in that sequence), in narrow windows:

    In Edge, the content on the right is cut off (not shown).

  • I hope you can fix the issue 😀

  • Microsoft Edge Team

    Changed Status to “Confirmed”

  • Hello,

    Thank you for providing this information about the issue. We have confirmed the problem, and are considering a solution for a future build of Edge. We are presently tracking this issue as a duplicate of an existing internal bug report. We look forward to additional feedback you may have on how we can improve Microsoft Edge.

    Best Wishes,
    The MS Edge Team

You need to sign in to your Microsoft account to add a comment.

Sign in