Repository navigation
core: scroll-settle-pixel - #948
Conversation
ScrollArea draws a touch coast unsnapped and snaps again at rest. The frame a coast ends (run out, or stopped by a press) now moves the viewport so the content's origin sits on a whole physical pixel, staying inside the scroll range, so the snapped frames after it draw the same geometry as the last coast frame instead of rounding every pane and card by up to a pixel. Agent-Team: linux Worker: claude Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PM note: how this PR will be handledWhat it is for: core: scroll-settle-pixel Rules that apply: none special. Things to watch (checked by rule):
What happens next:
A living status comment below is kept current. Nothing here is a merge decision. |
Where this PR standsStage: Done: approved What the PM needs before approving (ticks as it is met; the full CI runs only at the end, after the reviews are clean):
Reviews at the current commit (
4 earlier reviews are for older commits and will be redone. Latest fixes comment: https://github.com/fizzyedit/work/issues/576#issuecomment-6464194635 (1 finding answered) Updated 2026-10-28 10:12 UTC by the PM. This comment is edited in place. |
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Agent-Team: linux Worker: claude
Agent-Team: linux Worker: codex
Part of fizzyedit/work#575
Rework: work#606
Goal
Resolve the merge conflict for PR #948, per fizzyedit/work#606 and the newest PM ruling.
What changed and why
Combined both sides of the sole conflict in ScrollArea.testFrame: retain row-coordinate recording for the settle tests, and run main's release-velocity recording after deinit for either layout. Production code was merged by the harness without manual changes.
How it was verified
Formatting, lint, native build and unit tests pass. See GATES.md for all gate results and sandbox socket failures. Existing coast/rest, press/rest and burst-event release-velocity regression tests are retained; this merge adds no behaviour or new tests.
Not done / follow-ups
The harness stages and records the merge, pushes, and posts FIXES. No window capture was taken; the earlier PM ruling assigns it as a PM follow-up. This checkout's supplied origin/main merge target is f051d49; its local history has no #939 merge commit, so that sequencing prerequisite cannot be confirmed offline.
Changes (1 files, +113/-7)
Gates: 6 of 6 passed
scripts/check-fmt.sh(exit 0)scripts/zb build --summary all(exit 0)scripts/zb build test --summary all(exit 0)scripts/zb build test-integration --summary all(exit 0)scripts/zb build check-web --summary all(exit 0)scripts/zb build test-sdk-version --summary all(exit 0)