This API does not preclude future work from improving the ergonomics of those existing APIs. The minor improvements to window.open|move*() API behaviors have no effect on their poor ergonomics (synchronous, features string shape, etc.). This work is also of interest to Google Slides. WebKit: No signal We requested a position and are waiting for feedback. This work partly pursues compatibility with that behavior. Firefox supports cross-screen window.open/move*() requests. Gecko: No signal We requested a position and are waiting for feedback. 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. This work is included in the W3C Second Screen CG charter to seek consensus and support for broad interoperability: We expect low levels of risk in supporting permitted cross-screen placement requests, and falling back on legacy same-screen behavior otherwise. Existing window placement APIs generally use compatible multi-screen coordinates, but implementations often restrict bounds to the current screen. Search tags window placement, screen enumeration, window, open, moveTo, moveBy, requestFullscreen, screen, display, monitor, multi-screen, multi-display, multi-monitor, cross-screen, cross-display, cross-monitorįeature detection of new screen information APIs and Permission API integration allows sites to handle different levels of feature support. This feature unlocks modern multi-screen workspaces for web applications.īlink component UI>Browser>WebAppInstalls
The existing singular window.screen offers a limited view of available screen space, and window placement functions generally clamp bounds to the current screen. Adds new screen information APIs and makes incremental improvements to existing window placement APIs, allowing web applications to offer compelling multi-screen experiences.
0 kommentar(er)
