- From: <bugzilla@jessica.w3.org>
- Date: Wed, 24 Sep 2014 21:28:21 +0000
- To: public-browser-tools-testing@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26900 Bug ID: 26900 Summary: [WebDriver Spec]: Timeout persistence is undefined Product: Browser Test/Tools WG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: WebDriver Assignee: public-browser-tools-testing@w3.org Reporter: w3.org@zetafleet.com QA Contact: public-browser-tools-testing@w3.org CC: mike@w3.org Blocks: 20860 Current Selenium servers seem to reset the "implicit" timeout (and maybe others) every time a new page load occurs within a session. This behaviour is counter-intuitive; the specification doesn’t currently define whether/how timeouts should persist. My preference would be for timeouts to be global to the entire session, not reset on a page load, but this seems to go against how servers actually work today. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 24 September 2014 21:28:28 UTC