26900 2014-09-24 21:28:21 +0000 [WebDriver Spec]: Timeout persistence is undefined 2015-10-26 03:53:01 +0000 1 1 1 Unclassified Browser Test/Tools WG WebDriver unspecified PC All RESOLVED FIXED P2 normal --- 20860 1 w3.org public-browser-tools-testing ato mike simon.m.stewart public-browser-tools-testing oldest_to_newest 112136 0 w3.org 2014-09-24 21:28:21 +0000 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. 112150 1 ato 2014-09-24 22:34:26 +0000 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.