Consider new APIs for window bounds

w3c / window-management

Window Management API

https://www.w3.org/TR/window-management/

Other

96 stars 25 forks source link

Consider new APIs for window bounds #8

Open michaelwasserman opened 4 years ago

michaelwasserman commented 4 years ago

There are active proposals to deprecate some existing APIs related to window placement, for example: https://groups.google.com/forum/#!topic/mozilla.dev.platform/qvU_vbvBrsI https://bugzilla.mozilla.org/show_bug.cgi?id=1579584

It may be reasonable to offer new async (potentially permission-gated) APIs and deprecate the existing legacy/sync APIs, like:

window.outer[Width|Height]
window.screen[X|Left|Y|Top]
window.resize[To|By]()
window.move[To|By]()

The explainer already suggests a new window.setBounds(), and it may be worthwile to explore corresponding new window bounds accessor methods.

michaelwasserman commented 4 years ago

One use case for this functionality is arranging a grid of web app windows, something useful for financial dashboards, etc.

It might be reasonable to limit the existing outer[Width|Height] accessors to standalone web app windows (ie. not for tabbed browser windows), and perhaps just for windows of installed web apps.

Garbee commented 4 years ago

I agree with having restricted data sets in a normal site-mode but allowing more open access once an application is installed. Installation has some level of explicit trust built into the action, exploration of this area should be considered. We need to balance having access with preventing widespread mis-use and that seems like a good middle-ground that could be had in lieu of a permission check (to some extent.)

michaelwasserman commented 2 years ago

This is a reasonable enhancement to consider in the future.