Making Delete Session an atomic commad

Currently calling Delete Session also involves discarding all open top-level browsing contexts.  Unfortunately the side-effect of this is that you cannot reconnect a WebDriver session to UA’s same state.

Many of the existing Selenium- and WebDriver implementations make a distinction between closing the session and steps that might involve terminating the browser process.

Because the same effect can be achieved on the client API side through iterating over the windows and closing each one individually, I’d like the propose making Delete Session atomic, by not having it implicitly close the top-level browsing contexts on your behalf.

Since there may be implementation-specific post steps tied to deleting a session, such as terminating the browser process, this in practice would mean that a UA could choose to decide whether to close the contexts or not.  It would, however, mean that one could, for some UA’s, “continue” from the same state a WebDriver session left it in.

Received on Tuesday, 9 June 2015 21:04:13 UTC