WebView shows abnormal tile rendering after screen rotation
Reported by
julian....@mediatek.com,
Sep 19
|
||||||
Issue descriptionDevice name: Mediatek MT6739 based platform Android version: Android 9.0 WebView version: 69.0.3497.100 Application: com.google.android.gms/.auth.uiflows.minutemaid.MinuteMaidActivity Application version: GMS version: 9_201808 URLs (if applicable): https://accounts.google.com/embedded/setup/v2/android/identifier?source=com.android.settings&xoauth_display_name=Android%20Phone&canFrp=1&canSk=1&lang=zh&langCountry=zh_cn&hl=zh-Hans-CN&cc=tw&hide_status_bar=1&flowName=GlifSetupAndroid Precondition: 1. HD+ display(720x1440, we can reproduce this issue with "wm size 720x1440" on a 720P device) 2. Enable auto screen rotation Steps to reproduce: (1) Goto Settings->Accounts->Add account->Google (2) In Google account sign in page, rotation screen from 180->90->180 (3) After screen rotation animation, WebView shows abnormal tile rendering (4) Once user touch the screen, the display back to normal. Expected result: WebView display normally after screen rotation Actual result: WebView display abnormally after screen rotation Note: - Please check the attached screenshots and video. - We can't reproduce this issue on Pixel devices, the system performance of MT6739 is slower than Pixel, and the animation timing are different. - It seems the image used by Window animation of screen rotation was already abnormal, and WebView didn't update the final rendering result after screen rotation.
,
Sep 20
,
Sep 27
@mediatek friendly ping. Did you get a chance to try a lower Webview version? Can you uninstall updates on your device and try again?
,
Oct 18
@julian.yeh: Could you please respond to comment#1 and #3. This would help in further triaging. Thanks!
,
Oct 18
Hi, sorry for late reply. Android P's WebViewFactory hardcode WebViewChromiumFactoryProviderForP http://androidxref.com/9.0.0_r3/xref/frameworks/base/core/java/android/webkit/WebViewFactory.java#49 I think lower version's WebView doesn't contain the "ForP" class. That's why I didn't try a lower version WebView in Android P For public device, it's is hard to find a low-end Android P device like MT6739 now.
,
Oct 18
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
In the video, it's not clear to me when the touch in "Once user touch the screen, the display back to normal" step happens. On low performance device, having the layout of the page be out of date for a moment is probably expected, but if it only recovers after user touches the screen, then that's definitely a problem. Can you take a chrome trace of a single rotation, wait for 5 seconds, then touch that recovers the display. Instructions here:https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs#TOC-Capture-a-trace-from-Chrome-on-Android-with-DevTools- Choose "Manually select settings", then select everything on the left, and unselect everything on the right. Devtools should attach to all webviews on a userdebug device.
,
Oct 19
,
Nov 12
@julian.yeh: Could you please respond to comment#18. This would help in further triaging. Thanks! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ctzsm@chromium.org
, Sep 19Labels: Needs-Feedback