This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26900 - [WebDriver Spec]: Timeout persistence is undefined
Summary: [WebDriver Spec]: Timeout persistence is undefined
Status: RESOLVED FIXED
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency tree / graph
 
Reported: 2014-09-24 21:28 UTC by csnover
Modified: 2015-10-26 03:53 UTC (History)
3 users (show)

See Also:

Attachments

Description csnover 2014-09-24 21:28:21 UTC 
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.
Comment 1 Andreas Tolfsen 2014-09-24 22:34:26 UTC 
They are meant to be persistent for the duration of the session.  I see this as implicit with the current wording, but specifying it explicitly does no harm I suppose.