Scroll Anchoring Is Now Baseline, So Delete Your Layout Jump Workarounds

If you have ever watched a page jump because an image or advert loaded above the part you were reading, you have met the problem scroll anchoring solves. The browser keeps the content you are looking at in place when the page changes above it. Chrome and Firefox have done this for years. With Safari 27 enabling it and adding the overflow-anchor property, web.dev's September roundup lists scroll anchoring as Baseline Newly available.

That means you can stop treating it as a browser quirk. Any JavaScript you wrote to measure the scroll position, insert content and then restore the offset by hand is a candidate for deletion. Test it first, but the native behaviour is usually smoother and has fewer edge cases than a hand-rolled version.

The property you need to know is overflow-anchor: none. It stops an element acting as an anchor node, and it is the fix when anchoring fights something you have built deliberately. Chat windows that stick to the bottom, virtual lists and carousels are the usual suspects.

Our advice is to leave the default on, delete the workarounds, and add overflow-anchor: none only where you can name the component that needs it. Then reserve space for images and embeds anyway. Anchoring softens layout shift, but it does not replace giving media a width and height.