You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you load a page, the content streams in and the browser can perform multiple render passes. If in its initial render pass there is no scroll-start-target, but eventually after some more loading an element with scroll-start-target: auto appears, do we then scroll to the element? I assume yes we would want to scroll in this case since the only reason it wasn't present in the initial style / layout was it hadn't loaded yet.
Then what if we have a page that has fully loaded and we add a scroll-start-target: auto element to a scroller? Presumably we don't want to scroll to the element in this case as the scroll-start-target wasn't there originally. Arguably a site which fetches some content containing a scroll-start-target could want this, but it seems like an anti-pattern for scroll stability.
I think in the current spec it isn't clear exactly when we would consider new scroll-start-target elements, but we should define when it takes effect such that it has the behavior we expect.
maybe @flackr can help me articulate this 🙂
The text was updated successfully, but these errors were encountered: