Address Bar Suggestions Render at DPI of Primary Monitor instead of current monitor (in multi-monitor, multi-dpi setup)

Issue #7135715

Details

Author
Bryan C.
Created
Apr 7, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
13.10586
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

To Reproduce:

  1. Use a High-DPI device (ex: Surface Book at 200% DPI)
  2. Plug in external monitor that’s not High DPI (ex: 1080p 24" monitor at 100% DPI)
  3. Drag Edge Window to external monitor
  4. Click in the address bar
    Expected Result:
  • Window and all its elements should resize to the DPI of the monitor Edge is on.
    Actual Result:
  • Window resizes to the DPI of the monitor Edge is on, except some elements don’t, such as the Address Bar suggestions render at the DPI of the device’s primary monitor (in my case 200%) instead of the monitor the window is currently on (in my case 100%).
    See attached screenshot.

Attachments

1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Christian F.”

  • This appears to be fixed for address bar suggestions in the new Edge Build 14332, however scroll bars still render twice as wide on my 100% dpi secondary monitor (where my primary monitor is 200% dpi).

  • Microsoft Edge Team

    Changed Assigned To to “Christian F.”

    Changed Assigned To to “Dave B.”

    Changed Assigned To from “Dave B.” to “David S.”

    Changed Assigned To from “David S.” to “Daniel H.”

    Changed Status to “Confirmed”

    Changed Status from “Confirmed”

  • Scroll bars are still rendering twice as wide when moving Edge to my 100% dpi secondary monitor (where my primary monitor is 200% dpi) in build 14342…

    The address bar suggestions dropdown is however rendering at the correct dpi now :)

  • Scroll bars still render at 200% DPI width on 100% DPI external screen in build 14352. The arrow icon at the top/bottom of the scroll bar is however resized properly.

  • Hello,

    Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 14393 and is available in our latest public stable build.

    Best Wishes,
    The MS Edge Team

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

Sign in