Nested sticky position elements jump out of position when the page is scrolled

Fixed Issue #14298121

Details

Author
Peter W.
Created
Oct 19, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Fixed in build #
17.17619
Reports
Reported by 5 people

Sign in to watch or report this issue.

Steps to reproduce

See https://codepen.io/petewarman/full/ZXwobp/ and the attached screenshots for an illustration of the issue. In the example the whole sidebar uses sticky positioning, and both the sidebar’s header and footer use sticky positioning. When the page is scrolled in Edge 16 the sidebar header and footer elements appear to jump out of position.

Attachments

2 attachments

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Steven K.”

    Changed Assigned To to “bbrinza”

    Changed Assigned To from “bbrinza” to “Kevin B.”

    Changed Status to “Confirmed”

    Changed Status from “Confirmed” to “In code review”

  • Flag.

  • Microsoft Edge Team

    Changed Status from “In code review” to “In progress”

  • Thank you for the report! We have fixed this issue in the development build and you should have the fix available in one of the coming Windows Insider Preview build.

  • Microsoft Edge Team

    Changed Status from “In progress” to “Fixed”

  • Please review this codepen:
    https://codepen.io/StijnDeWitt/pen/gKMNMJ?editors=1100
    It has a header bar which is sticky to the top, which uses position:sticky on nested elements to reveal a drop-shadow on scroll.

    In Chrome, Firefox, Opera this works as intended. Not sure about Safari…
    In Edge, the inner divs do not stick and I cannot figure out why not. This bug is the closest resemblance to my issue I have found so I wonder if you guys maybe forgot some edge case I am stumbling into? Or am I just doing it wrong?

    Could you maybe have a look and tell me if I should be trying to fix my code or whether I might have hit this (a similar/related) bug? I cannot test the insider build as far as I know so hoping you could let me know whether I should spend energy on this… If it is already fixed in insider build I will happily wait for that to come out :)

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

Sign in