Adds new screen information APIs and makes incremental improvements to existing window placement APIs, allowing web applications to offer compelling multi-screen experiences. The existing singular window.screen offers a limited view of available screen space, and window placement functions generally clamp bounds to the current screen. This feature unlocks modern multi-screen workspaces for web applications.
Feature detection of new screen information APIs and Permission API integration allows sites to handle different levels of feature support. Existing window placement APIs generally use compatible multi-screen coordinates, but implementations often restrict bounds to the current screen. We expect low levels of risk in supporting permitted cross-screen placement requests, and falling back on legacy same-screen behavior otherwise. This work is included in the W3C Second Screen CG charter to seek consensus and support for broad interoperability: https://webscreens.github.io/cg-charter/ The Screen IDL interface duplicates EventTarget members to mark them RuntimeEnabled for this experiment, since using interface inheritance would also change the stable JS API.
The minor improvements to window.open|move*() API behaviors have no effect on their poor ergonomics (synchronous, features string shape, etc.). This API does not preclude future work from improving the ergonomics of those existing APIs. Extending the requestFullscreen dictionary with an optional screen should pose no ergonomic risks. The new multi-screen information APIs have some minor potential ergonomics issues around naming, object comparison, and event handling that we hope to resolve using OT feedback. See https://github.com/webscreens/window-placement/issues for more details. New dual-screen and foldable screen devices are entering the consumer market, increasing the complexity of exposing reliable and actionable screen information for all device form factors. Additionally, operating systems and their window managers support different levels of screen placement APIs, and new paradigms may emerge that complicate the availability of window placement features. See the Second Screen's "Form Factors Explained" report for more explorations on these topics: https://webscreens.github.io/form-factors/
This feature incrementally extends existing screen information and window placement interfaces with basic multi-screen support. This immediately enables new compelling experiences through progressive enhancement of existing applications.
Security and Privacy risks are explored in repo documents: <https://github.com/webscreens/window-placement>. That analysis and review uncovered minimal risks. Privacy concerns center around fingerprinting screen information, while security risks center around deceptive, surreptitious, or annoying window placements, such as clickjacking. Gating new functionality with a permission helps mitigate these concerns, and may aid or inspire similar protections for legacy API behavior with similar abuse vectors. The overall added risks are low and further mitigated by limiting to secure contexts, a permissions policy, providing origin-scoped generated screen ids that reset when cookies are cleared, being selective about display information to expose, and continuing to prevent off-screen window placement.
We want developer feedback around the feature's performance and applicability in production scenarios with a broad set of screen configurations. The API shape has changed significantly since the first Origin Trial (M86-M88), and we would like to get additional developer feedback before shipping. - Does the feature permit sufficiently expressive placement requests? - Does the permission model/flow integrate well with product design? - Do any screen configurations or placement scenarios pose unforeseen challenges? At least one major customer inside Google wants to use this API in their product. We want to learn from their deployment experiences and collect metrics on feature subsets.
N/A
None.
New and existing screen and window APIs are readily debuggable in existing developer tools.
All Blink platforms have some support for multiple displays, but may restrict the placement and sizing of windows. The overall API will be exposed everywhere except WebView, as developers have primarily voiced interest for use cases in desktop applications, and the added complexity strongly exceeds developer enthusiasm for WebView support. All other Blink platforms will be supported.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEsbcpV_s7jHYVhdGaxiG83w0VVi1k-ze8apqL5aqD%2BSawnpGg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfXRdkfHdDBEJ5MgeCzQbahOrbmJC3N4pCFA__Sw3Aem9A%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALgRrL%3Dnra3ZG9D4BgNz6Okye3qfcFpc6DS2FFRVZ%2BrchGWDag%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3a08c6c0-7fce-42b0-bbd9-b910f1c9dc46n%40chromium.org.