For apps that have no control over the content, you may want to try the _AUTOSIZING algorithm or just leave it on the default layout and hope for the best. As a shortcut that closely emulates the old behavior, give a shot to this method posted on StackOverflow. If they can directly control the content being rendered by the WebView, such as eBook readers and web apps, it's probably best to just make these pages mobile-friendly. Even some eBook readers have been known to render content to a WebView.ĭevelopers will find themselves in varying situations. Naturally, we can also see this issue popping up in several apps that include embedded browser windows, something commonly found in Twitter clients, forum readers, RSS clients, and many others. Some popular alternative browsers like Dolphin and Lightning offer their own customizations, but still use the built-in WebView for rendering. Losing text reflow in Chrome and the AOSP browser is certainly a problem, but it reaches farther than just a couple of browsers anything relying on the WebView class has lost this feature. It's worth pointing out that one of the longest standing criticisms of Chrome for Android is that text reflow has always been disabled. Despite being based on WebKit, which was able to reflow text, Blink seems to lack this ability. ![]() Chrome for Android officially made the switch in July with v28, and the AOSP WebView followed suit with KitKat in October. The intent was to remove some clutter and add deeper customizations. You see, back in April 2013, Google announced that its Chromium Project, the open source component of the Chrome web browser, would be forking WebKit to create a custom layout engine called Blink.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |