If device implementations provide a complete implementation of the
android.webkit.Webview API, they:
Mozilla/5.0 (Linux; Android $(VERSION); \[$(MODEL)\] \[Build/$(BUILD)\]; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 $(CHROMIUM_VER) Mobile Safari/537.36 * The value of the $(VERSION) string MUST be the same as the value for android.os.Build.VERSION.RELEASE. * The $(MODEL) string MAY be empty, but if it is not empty it MUST have the same value as android.os.Build.MODEL. * "Build/$(BUILD)" MAY be omitted, but if it is present the $(BUILD) string MUST be the same as the value for android.os.Build.ID. * The value of the $(CHROMIUM_VER) string MUST be the version of Chromium in the upstream Android Open Source Project. * Device implementations MAY omit Mobile in the user agent string.
The WebView component SHOULD include support for as many HTML5 features as possible and if it supports the feature SHOULD conform to the HTML5 specification.
[C-1-3] MUST render the provided content or remote URL content in a process that is distinct from the application that instantiates the WebView. Specifically the separate renderer process MUST hold lower privilege, run as a separate user ID, have no access to the app's data directory, have no direct network access, and only have access to the minimum-required system services over Binder. The AOSP implementation of WebView meets this requirement.
Note that if device implementations are 32-bit or declare the feature flag
android.hardware.ram.low, they are exempted from C-1-3.
If device implementations include a standalone Browser application for general web browsing, they:
However, If device implementations do not include a standalone Browser application, they: