Reader keeps the old scroll position when the next text is shown #73
Labels
No labels
area/ci
area/desktop
area/packaging
area/protocol
area/reading
area/ui
area/web
area/writing
kind/bug
kind/feature
kind/infra
kind/request
needs/user
parked
perf
security
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
littlefox/neokom#73
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
User report (v0.1.0): read a very long text, scroll to its end, press space. The next text is shown without scrolling back to the top. If it is short enough to fit on the screen, there is no way to scroll up: you see half of it at best, nothing at worst.
Cause: main.reading is its own scroll container (overflow-y: auto) and keeps its scrollTop when its content is replaced. Chromium clamps it to the new content; WebKitGTK (desktop) can leave it past the end with no scrollbar.
Expected: every newly shown text, conference status, composer or settings pane starts at the top.
Merged in #74 (CI run #108 green), released in v0.1.2. scroll.spec.ts reproduces the report (272 px down instead of 0 without the fix) and checks that mark/unmark keep the place. Not yet tried by hand in the desktop app (WebKitGTK), where the 'stuck past the end' symptom appears.