Partially rendered content if used within NestedScrollView in Oreo+
Reported by
fik...@gmail.com,
Oct 12
|
||||
Issue descriptionTHIS TEMPLATE IS FOR FILING BUGS ON THE ANDROID SYSTEM WEBVIEW. GENERAL WEB BUGS SHOULD BE FILED USING A DIFFERENT TEMPLATE! Device name: Nexus 5 Emulator Android version: 28 (also happened in 26) WebView version (from system settings -> Apps -> Android System WebView): WebView Shell 1.0 Application: Application version: URLs (if applicable): Steps to reproduce: (1) Create a project with WebView within NestedScrollView (2) Fill with 100 or more lines of "<h1>$i</h1>" (3) Run in emulator (not real device) (4) Scroll down Expected result: It must rendered until 100 Actual result: Cut at 92
,
Oct 15
@ fikr4n: Could you please provide sample apk/test file to test this issue from our end. Also please provide android version and chrome version you are seeing this issue on. This would help in further triaging. Thanks!
,
Oct 16
Thank you. Gmail prevents me to attach the APK, so I place it in https://github.com/fikr4n/webviewtest/releases/tag/v1.0, the source code is available too. It is run on emulator with Android version 9 (API Level 28). Unfortunately I don't know how to get the Chromium version, in *Settings > Apps and Notifications > See all apps*, I found only WebView Shell (version 1.0).
,
Oct 16
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 18
Works fine on a real phone with touch screen and doing touch scrolling. Also shows header and footer at top and bottom. What's happening is touch events are intercepted before they reach webview, and all webview sees is that it's being translated by NestedScrollView. Webview team generally recommends against doing this where the webview size is gigantic and scrolling happens by "translation", since that can cause a lot of problems in corner cases. Unless you control the content loaded into the webview so that you can test it works well enough, this is probably not a good idea. I'm not sure how exactly you are scrolling it on the emulator though. Perhaps it's triggering a different input path.
,
Oct 19
Specifically, it's discouraged for you to use wrap-contents height on a webview or parent view of webview (unfortunately wrap-contents height the default) I'm going to close this since your specific apps seems to work fine on a real phone |
||||
►
Sign in to add a comment |
||||
Comment 1 by chelamcherla@chromium.org
, Oct 15