diff --git a/overview.html b/overview.html index 61bfd65..cef17f0 100644 --- a/overview.html +++ b/overview.html @@ -18,8 +18,6 @@ so rendering should be much more consistent between the WebView and Chrome.

The new WebView also supports remote debugging using the Chrome DevTools.

-

[[TOC]]

-

WebView FAQ

What version of Chrome is it based on?

@@ -28,6 +26,15 @@ using the Chrome DevTools.

Chrome for Android version 30. The WebView does not have full feature parity with Chrome for Android and is currently given the version number 30.0.0.0.

+

Will the new WebView auto-update?

+ +

Evergreen browsers (like Chrome and Firefox) auto-update and keep their users up to date so they +can view the web through a modern feature set. As a developer, this ensures your choices aren’t +limited to a lowest-common denominator browser from years ago, but rather are keeping pace with the +modern web. Your apps inside a WebView are just as important and deserve a runtime that keeps users +up to date. There are large engineering and logistical challenges. We're not quite there yet, but +we're working on it.

+

What is the default user-agent?

The new WebView adds Chrome/_version_ to the user-agent string. Sample @@ -76,12 +83,6 @@ WebView, including:

  • Form validation
  • -

    Will the WebView have a six-week release cycle like Chrome?

    - -

    WebView will continue to be tied to releases of the Android platform for the -time being. However, sharing code with Chrome for Android will make it easier to keep -the WebView up to date.

    -

    What does the new WebView mean for developers?

    This is a big change from the original WebView as it brings a new set of HTML5