Doogee S55 64Gb+4Gb Dual LTE [31/118] Web compatibility

remain available to 32-bit native ARM code, either through native CPU support or through

software emulation:

SWP and SWPB instructions

SETEND instruction

CP15ISB, CP15DSB, and CP15DMB barrier operations

If device implementations include a 32-bit ARM ABI, they:

[C-2-1] MUST include the following lines in /proc/cpuinfo when it is read by 32-bit ARM

applications to ensure compatibility with applications built using legacy versions of

Android NDK.

Features: , followed by a list of any optional ARMv7 CPU features supported by

the device.

CPU architecture: , followed by an integer describing the device's highest

supported ARM architecture (e.g., "8" for ARMv8 devices).

SHOULD not alter /proc/cpuinfo when read by 64-bit ARM or non-ARM applications.

3.4. Web Compatibility

3.4.1. WebView Compatibility

If device implementations provide a complete implementation of the android.webkit.Webview API, they:

[C-1-1] MUST report android.software.webview .

[C-1-2] MUST use the Chromium Project build from the upstream Android Open Source

Project on the Android 8.0 branch for the implementation of the android.webkit.WebView API.

[C-1-3] The user agent string reported by the WebView MUST be in this format:

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 value of the $(MODEL) string MUST be the same as the value for

android.os.Build.MODEL.

The value of 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 .

3.4.2. Browser Compatibility

If device implementations include a standalone Browser application for general web browsing, they:

[C-1-1] MUST support each of these APIs associated with HTML5:

application cache/offline operation

<video> tag

geolocation

Page 31 of 118