Intent to Ship: Account for System UI elements in screen.avail properties on Android

[Chromestatus]

Contact emails

ren...@google.com

Explainer

https://developer.mozilla.org/en-US/docs/Web/API/Screen

Specification

https://developer.mozilla.org/en-US/docs/Web/API/Screen

Design docs

https://docs.google.com/document/d/1AccF_jc0ZgnM10YZSRzMjoTyJefKUH1A4OwaDcm1s9Y

Summary

The screen.avail properties account for system UI elements when calculating available screen space on Android. This provides developers with the exact usable display area needed to accurately place application windows on Android.

Blink component

Blink>Screen

Web Feature ID

screen

Motivation

These changes in screen.avail properties provide developers with the exact usable display area needed to accurately place application windows. Consequently, popups and windows appear in the correct locations without overlapping the operating system interface.

Initial public proposal

No information provided

TAG review

No information provided

TAG review status

Not applicable

Goals for experimentation

None

Risks

Interoperability and Compatibility

No information provided

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

No information provided

Debuggability

No information provided

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

No

Is this feature fully tested by web-platform-tests?

No

Flag name on about://flags

android-use-correct-display-work-area

Finch feature name

AndroidUseCorrectDisplayWorkArea

Rollout plan

Will ship enabled for all users

Requires code in //chrome?

False

Estimated milestones

No milestones specified

Anticipated spec changes

Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).

No information provided

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/4824062942642176?gate=5662595311861760

Links to previous Intent discussions

Intent to Prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69d79280.050a0220.2357b3.0230.GAE%40google.com

This intent message was generated by Chrome Platform Status.

[Alex Russell]

This feels like a useful change, but I'm wondering if we really have no input from developers?