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
{{ message }}
Repository navigation
Commit 571d5cd
Browse filesBrowse the repository at this point in the historyBrowse files
fix(scroll): name what a scroll observed and read an edge off one tree
Two pieces the directional-scroll answer needs, with no behavior change on its own.
`movement` is the vocabulary a scroll uses to say what happened to the surface: `moved`,
`at-edge`, `unchanged` when the visible content did not change, and `unobserved` when the
command could not compare anything. It is absent when the runtime cannot read a screen at
all, so a caller never has to guess whether a missing claim means "did not move".
`readScrollEdgeState` is the one pure door into the edge analyzer — the question
`canScrollFurtherAtEdge` and `scrollSurfaceFingerprint` already ask, exposed with the frame
of the container that answer was taken on. Without `containerRect`, `canScroll: false`
cannot distinguish content that ends here from a tree that named no container, and a caller
checking whether its gesture landed inside the list has nothing to check against.
0 commit comments