-
Notifications
You must be signed in to change notification settings - Fork 642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[cssom-view] Proposal: Enabling new multi-display and multi-window experiences #4615
Comments
FYI @zcorpan |
@michaelwasserman will these proposals have any effect on the existing |
AFAICT, the existing My current thought is that getScreens() should return static Screen objects, the API should offer an Other options are certainly on the table; I'd appreciate thoughts and feedback on this open screen-enumeration issue: webscreens/screen-enumeration#12 |
Thanks @michaelwasserman! Another related consideration is if you want |
Per recent feedback from TAG, we'd like to get this group's thoughts on deprecating the existing Thoughts on that or feedback on webscreens/window-placement are greatly appreciated! @foolip the proposal favors exposing static snapshots, so it explores exposing |
I'd like to raise awareness and request feedback for a couple proposals relevant to this working group. They touch on numerous aspects of the Screen and
[Window](https://drafts.csswg.org/cssom-view/#extensions-to-the-window-interface)
interfaces. Thanks in advance for any issues filed, or other discussion/feedback shared!Screen Enumeration API
This proposal aims to give web developers information about the set of connected physical displays, and considers additional display properties that may be useful beyond the current Screen interface.
Window Placement API
The ability to open and move windows across the full set of connected displays is unstandardized and the current behavior is inconsistent between implementers. This proposal aims to give web developers standard means to manage their web content in modern windowing environments.
The text was updated successfully, but these errors were encountered: