RE: Proposal for New Window command

Yeah I think the main use case is creating a new tab without using window.open. It might also make multi-tab testing for things like services workers a little simpler. I also find Marc’s suggestion perfectly fine.

From: Simon Stewart [mailto:simon.m.stewart@gmail.com]
Sent: Tuesday, November 22, 2016 12:49 PM
To: Andreas Tolfsen <ato@mozilla.com>
Cc: public-browser-tools-testing <public-browser-tools-testing@w3.org>; Marc Fisher <fisherii@google.com>
Subject: Re: Proposal for New Window command

On Tue, Nov 22, 2016 at 8:15 PM, Andreas Tolfsen <ato@mozilla.com<mailto:ato@mozilla.com>> wrote:
Marc Fisher <fisherii@google.com<mailto:fisherii@google.com>> writes:

> > This could be implemented as a POST to /session/{session
> > id}/window/new as POST /session/{session id}/window is occupied by
> > Switch To Window, or we could switch them around.  It would return
> > the window handle of the new window, and would be guaranteed
> > blocking, unlike other techniques mentioned above.
>
> Or  POST /session/{session id}/window without a window handle/name
> could create a new window.

Yes, that is better.

I don't think it's a great idea to add this command, but….

I hear Andreas's original comments, and understand where he's coming from, but for the last 10 years both Selenium Core and WebDriver managed to meet testing needs without it. So, it's not a hard requirement for the "testers" audience. So it feels that this is primarily aimed at browser vendors or spec authors. If they need this method for some reason, we should probably add it.

If we do add it, Marc's suggestion seems sensible to me.

Simon

Received on Tuesday, 22 November 2016 21:33:00 UTC