bikeshed: consider naming the permission multiscreen instead of window-placement

[quisquous]

A suggestion from @inexorabletash

[michaelwasserman]

This is a reasonable suggestion, but some suggested enhancements (e.g. opening a popup in fullscreen, minimizing or maximizing the window) and related ongoing work in the web platform (potential efforts to deprecate window.moveTo(), etc. without something like a window-placement permission) might be cause to keep the window-placement name or some other name. This may merit further consideration before an API mvp milestone.

[quisquous]

I agree with msw's comments above, re: actions that may not require "multiple screens" but still may be placed behind this permission. I am inclined to keep this as window-placement, unless there's some stronger reason to change.

@inexorabletash, do you see a risk here where there are future theoretical actions that do not fit in the "window placement" naming bucket but that would we would want to put behind this permission?

[inexorabletash]

Nah, I'm good with keeping it as is. Thanks for considering!