- From: James Graham <james@hoppipolla.co.uk>
- Date: Wed, 04 Feb 2015 22:41:14 +0000
- To: public-browser-tools-testing@w3.org
On 04/02/15 20:53, David Burns wrote: > The main use case I have is instances where you want to be able to > restart the browser but maintain the same session id so that we can > debug problems easier from logs. This has been implemented like that in > Gecko for the Firefox Hello and Firefox Desktop automation teams. I don't entirely follow why it's needed. For pure debugging it seems much better to know that a new session started rather than being misled into thinking that you are actually using the old session. > There might be other times where we want to be able to debug session > details being moved from point to point and put our own session id so > that it might be easier to follow. This would be useful with things like > Selenium Grid. I think this is outweighed by the chance of bugs and confusion if a remote ever overrides the locally-provided session id.
Received on Wednesday, 4 February 2015 22:41:38 UTC