Android Oreo enables the multi-process mode
for WebView components from Nougat as the default and adds a new set of APIs that provide version information, better ways to terminate a web view window, a method to determine the priority of rendering a web view, and the Google Safe Browsing API.
Not exact matches
Unfortunately
for Android users, this is exactly what Google did when they chose to stop supporting
WebView for those with older versions of their operating system — a shocking... [Read more...]
It is the responsibility of the Reading System implementor to account
for the security and privacy implication of
WebView - to - application communication.
A recent revelation that Google is no longer developing security patches
for the «
WebView» component of Android in Jelly Bean and earlier has once again put a spotlight on Android security, and the challenges involved with securing the one billion or so active devices.
Some Reading Systems on mobile devices are implemented using a system - provided web component (often referred to as a
WebView)
for the rendering of content.
For example, the user clicks a button and it opens up a
webview of this link:: / / upload.wikimedia.org/wikipedia/commons/thumb/f/f2/Xamarin-logo.svg/1200px-Xamarin-logo.svg.
WebView enhancements: Android O enables multiprocess mode by default and adding an API to let your app handle errors and crashes,
for enhanced security and improved app stability.
The rest of the changes are under the hood, with features including apps being able to manage wallpaper colors, apps alerting Google to when a
WebView instance sends folks to a website that sets off Safe Browsing, developers better able to target their apps
for low - RAM devices, and a few other adjustments.
Ardian Ludwig, Google's lead engineer
for Android security, on Friday revealed the decision was due to the complexity of applying patches to older branches of WebKit - the browser engine that was used in
WebView and Chrome until Google forked WebKit into Blink
for Chrome.
There are also some major optimizations to the Android Run - Time (ART) responsible
for handling your apps and
WebView has also seen some enhancements you're unlikely to ever even notice.
In June we introduced preview support
for, which is now supported by default in Microsoft Edge starting with Microsoft EdgeHTML With this change, Hosted Web Applications and the
WebView in any Universal Windows Application can now benefit from asm - optimized... Read more
For developers, Android Oreo introduces
WebView, Java 8 language APIs (Application Programming Interfaces), a Neural Networks API, Autofill framework, notification channels, AnimatorSet, autosizing TextView, new media features, unified layout margins and padding, speech output, app categories, and fonts in XML format.
WebView supports Safe Browsing
for Android Instant Apps, too.
WebView is the part of the Android OS responsible
for rendering web pages in most Android apps.
That means users won't have to log in again in the
WebView if they're already logged in with Chrome
for that respective page.
Other features are the ability to show custom buttons on top of
WebView frames and content pre-fetching
for faster loading times.
Android Oreo is mostly designed to improve the security and functionality of its devices, and it takes quite a few cues from iOS in doing so — Oreo focuses on limiting what apps can do in the background, gives apps tools
for creating adaptive icons, adds wide - gamut color support
for third - party apps, audio and
WebView enhancement APIs, and more.