Wierd scrolling issues with position:fixed;left:0; inside div with position:fixed;top:0;

Issue #14602923 • Assigned to Bogdan B.


Morris J.
Nov 10, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Scrolling https://output.jsbin.com/yivewev/quiet has a variety of rendering problems (using Microsoft Edge 41.17025.1000.0).

We are tring to acheive something like Excel frozen heading with frozen left column too - and our technique works perfectly in Chrome, Firefox, and Safari (Safari iOS does a little heading jitter on vertical scrolling but not nearly as bad as Edge).

See video:

Bug #1 (approx 5 seconds into video): scrolling down while horizontal scroll at hard left loses some names (blanks after Malone, Wendy). The names appear again (around 6 seconds) when we start scrolling right.

Bug #2 (around 10 seconds into video): scrolling left/right causes juddering of Top Left (“Employee”).

Bug #3 (from 15 seconds to 25 seconds): zoom in a little. Scroll up and down and the top fixed heading has subpixel rendering issues of juddering, font blurring, and background exposing above and below the headers. Must be scrolled right a bit to occur.

Bug #4 (from 25 to 30 seconds): scrolling left and right causes rendering problems in header (different when zoomed than from when not zoomed) including subpixel problem where background is showing through at far right of header.

Bug #5 (approx 32 second to end): change the scrolling veiwport from a div to the body (click [use body scrolling] button), and all the fixed headers go completely wrong.

The #1 above is a real issue because it doesn’t fix itself and clients would be affected. #2, #3 and #4 are cosmetic during animation so not so bad. #5 is only FYI - we don’t need that functionality (although someone else will surely hit the problem).

Appendix: Note that we originally opened issue
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/13592652/ but that issue has been fixed (but not closed).


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Steven K.”

  • Hi Morris,

    I knew this looked familiar.  I was able to repro a couple of the issues.  I need to read your problem statements again to be sure I am not missing anything.  The video is very helpful.  Thank you for taking the time to create that.

    Not sure why the fix didn’t make it into the release.  :-/  We will investigate.

    Appreciate the support,


  • Microsoft Edge Team

    Changed Assigned To to “wptcomptri@microsoft.com”

  • Steve, these bugs are different from what I originally reported for bug 13592652 (retrograde scrolling and severe display faults), even though it is using the exact same test. Although I did allude to these bugs in a previous comment, they really need a new issue and the video shows them better than the comment.

    In fact I probably should have split this into multiple issues because there are multiple orthogonal problems, but I am hoping support or the developer can internally create multiple issues more sensibly (and with a better internal information than I can).

  • Hi Morris,

    Yes, what you have provided is sufficient and you are correct in this case that the dev team will be able to breakdown the issues.

    I am also making a note about this not being the same issue as before.  Thank you for the correction and details.


  • Microsoft Edge Team

    Changed Assigned To to “Christian F.”

    Changed Assigned To from “Christian F.” to “Bogdan B.”

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

Sign in