Page Scroll Bar is Still Rendered at 200% Width on External 100% DPI Monitor if Primary Monitor is 200% DPI (Like Surface Book)

Issue #7831701 • Assigned to Bogdan B.


Bryan C.
Jun 9, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

The primary Scroll Bar does not respond to DPI changes when the Edge Window is dragged between monitors with different DPIs, but instead keeps the DPI of the primary monitor.

To reproduce on a Surface Book:

  1. Plug external 100% DPI monitor into Surface Book (or other computer with a 200% DPI primary monitor)
  2. Open Edge
  3. Drag the Edge Window to your 100% DPI External Monitor

Observe the Following:

  • Note that the primary page Scroll Bar is enormous as it’s still rendering at 200% DPI.
  • Note that other scroll bars within a document (ex: textareas, iframes, etc) properly render at 100% DPI.
  • Note that the up/down arrows at the top/bottom of the primary scroll bar DID properly rescale to 100% DPI even though the rest of the scroll bar did not.


1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Ibrahim O.”

    Changed Assigned To to “Rick J.”

    Changed Assigned To to “Bogdan B.”

  • You probably already know this, but this is still a problem in Build 14371.

  • Still a problem in 14376

  • This is still a problem in build 14388.

    I also hooked up a 150% scale 4k monitor, and sure enough, the scroll bar still renders at 200% width instead of 150% width on that monitor because my primary monitor (the Surface Book) is set to 200% dpi.

  • Still a problem in 14393

  • Still a problem in 14393.5

  • Still a problem in 14393.51

  • Still a problem in 14393.82

  • Still a problem in 14393.187. Chrome and Firefox do not have this problem.

  • Still a problem in 14971… Hello!!! Is anyone there??? THIS IS A SIMPLE BUG TO FIX!

  • Will this ever be fixed? Still busted in 14986.


  • Still broken in 15031. Edge is showing serious promise lately. Really hope a fix for this can make it before Creators Update launch!

  • Still broken in 15046

  • Still broken in 15048

  • Still broken in 15058

  • Still broken in 15061

  • Still broken in Creator’s Update 15063. Hopefully something you can get to this year.

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

Sign in