Re: [w3ctag/design-reviews] Early design review of the **updated** Multi-Screen Window Placement API (#602)

> I find `Promise<Screens> getScreens();` a bit confusing due to `.screens` property.

We have that filed on https://github.com/webscreens/window-placement/issues/50 as a place to discuss.  As you say, naming is really hard.  I don't think anybody has come up with a better name yet and so we've been punting on that so far.

> I'm wondering if it would help developer ergonomics to also allow an optional screen argument to the Window.moveTo() method, which if passed, makes the x, y coordinates relative to the passed screen. If added, a similar mechanism should be added to Window.open() (perhaps changing the features argument from a string to an object).

I worry that it might be confusing to have the coordinates change their semantics if an optional third parameter is present.  I wonder if it might be better to pick one of (a) x and y are relative with optional screen or (b) x and y are absolute, no screen parameter.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/602#issuecomment-831598407