targetSdkVersion <= 20 in manifest causes strange rendering/behavior
Reported by
anthonyo...@gmail.com,
Sep 5 2016
|
|||||
Issue descriptionExample URL: http://arstechnica.com/gadgets/2016/08/android-7-0-nougat-review-do-more-on-your-gigantic-smartphone/ Steps to reproduce the problem: 1. In Android manifest, set targetSdkVersion to 20 or less 2. Enable WebView JavaScript 3. Load URL http://arstechnica.com/gadgets/2016/08/android-7-0-nougat-review-do-more-on-your-gigantic-smartphone/ 4. Scroll down page, allow more articles to load, page goes gray What is the expected behavior? Page should not turn gray as it is scrolled down. What went wrong? Apps that target 20 or below have strange rendering like this. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 53.0.2785.90 Channel: n/a OS Version: 5.1.1 Flash Version: N/A Similar to this rejected issue: https://bugs.chromium.org/p/chromium/issues/detail?id=619346
,
Sep 9 2016
I am getting more and more reports of this issue. For example, the buttons at the bottom of profiles on this dating site are cut off: http://www.thaicupid.com/en/profile/showprofile/ID/4351924
,
Sep 9 2016
Another report that full screen video on this site displays so large that only a portion of the video is in the viewport, with no way to see the rest: http://www.cnet.com/videos/this-speedy-lg-washer-struggles-with-stains/ This happens when target SDK is 18 or lower, and so perhaps more similar to this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=619346
,
Sep 9 2016
If the problem is in your own application, then the same advice as issue 619346 applies: update your app to target a more recent SDK version, to avoid the workarounds we do for backward compatibility.
,
Sep 11 2016
No, the bug causes rendering problems in any app using WebView with target less than or equal to 20. I wish I could tell you where the bug or bugs are in the chromium code, but I do not even know where to begin to look.
,
Sep 11 2016
I have another report that when target SDK is set to 18 or lower, fastmail.com loads the desktop version of the site even though mobile user agent is used. With target of 19 or higher, the site loads the mobile version as expected.
,
Sep 13 2016
Can you suggest a *specific* application in which you can reproduce this problem, then?
,
Sep 13 2016
I tried webview's browser shell (link below - set the target sdk to 19) and did not see a problem. https://cs.chromium.org/chromium/src/android_webview/tools/system_webview_shell/
,
Sep 18 2016
please provide a specific application as requested so we can repro.
,
Sep 23 2016
,
Sep 30 2016
Thank you for providing more feedback. Adding requester "sgurun@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 27 2016
I continue to receive reports about this issue. Here is the latest site: http://www.alphr.com/science/1004774/what-polluted-chinese-cities-can-learn-from-london-s-1952-killer-fog Again, if target is 20 or lower and JavaScript is enabled then the bottom portion of the web page--most of the web page actually--is blank.
,
Dec 20 2016
Here is another report that happens when target SDK is 18 or lower. Visit this site: http://www.aftonbladet.se/nyheter/brottscentralen/a/o2m9V/hon-avslojade-bankomatbluffen If target is 18 or lower, and whether JavaScript is enabled or not, a strange red color is applied as in attached image 18.png. If target is 19 or higher, page renders normally as in attached image 19.png.
,
Jan 2 2017
Another site that misbehaves depending on target SDK, regardless of JavaScript, is: https://www.teabox.com/tea/avongrove-special-summer-darjeeling-black Could these issues be related?
,
Jan 4 2017
Attached screenshots provided by user show WebView inconsistencies described in last comment, #14 above.
,
Mar 13 2017
Cleaning up sheriffbot label "Needs-Review" label as a part of modified "Needs-Feedback" sheriffbot rule. [ref bug for cleanup 684919]
,
Sep 13 2017
Effort from the triage Team: There is no active investigation / updates since the last couple months,closing the issue. Feel free to reopen if needed. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by tkent@chromium.org
, Sep 5 2016