Refactor, Fixes, and functionality to avoid processing nested scroll events on internal webview elements scrolls #8
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.
🎟️ Jira tickets
ANDROID-13326
ANDROID-11710
🥅 What's the goal?
I decided to revert the "helper" approach to extract to an specific file code extracted from NestedScrollView support library code, this was leading to issues due methods not calling directly WebView methods (Specially all the ones related with NestedScrollingChild3 interface implementation). So I just added this directly to the NestedScrollWebView class, identifying support library code with an specific comment block (trying to keep it as unaltered as possible for future updates).
Fixed also an issue where scroll was maintained after navigating to a new page (ANDROID-11710) -->
Record_2023-05-11-10-14-24.mp4
Record_2023-05-24-19-03-54.mp4
Record_2023-05-24-19-02-56.mp4