fix: handle sticky container check in cached navigations scroll path
FragmentInstance (from React's Fragment ref API) does not expose parentElement, so the previous approach of casting to access it silently returned undefined. This caused the sticky/fixed container check to always fail in InnerScrollHandlerNew, meaning the sticky header slot still consumed the shared scrollRef and prevented scroll-to-top. Fix: add a zero-layout-impact marker <span style=display:contents> inside the Fragment. Its ref provides a real DOM element we can walk up from to detect sticky/fixed ancestors.
Showing
Please
register
or
sign in
to comment