fix: stabilize Android reader scrolling#585
Open
codedogQBY wants to merge 1 commit into
Open
Conversation
Owner
Author
|
补充一份更细的验证 checklist,方便合并前复核: 已执行:
已知阻塞,不归这个 PR:
建议真机回归:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #548
Fixes #565
Fixes #567
Fixes #571
Analysis
The 1.3.5 reports describe the same Android scroll-mode regression from different angles: sticky/short scroll distance, jumping to non-adjacent paragraphs, line/content misalignment, and occasional flicker during long reading sessions. The common path is continuous scroll relocation: Foliate was still intercepting touch movement in scrolled mode and manually mutating container position, while every relocate event immediately crossed the WebView bridge and triggered multiple React Native state/context updates. That made Android scroll feel blocked or jumpy under pressure.
Verification