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 27950 - executeScript and executeAsyncScript algorithms should respect the script timeout
Summary: executeScript and executeAsyncScript algorithms should respect the script tim...
Status: NEW
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-03 16:46 UTC by Andreas Tolfsen
Modified: 2015-02-19 22:53 UTC (History)
2 users (show)

See Also:


Attachments

Description Andreas Tolfsen 2015-02-03 16:46:25 UTC
The executeScript and executeAsyncScript algorithms make no mention of the script timeout global.  They should timeout when this is reached, or run indefinitely if -1 (negative integer) is given.

Section 13.1.1 mentions that "script timeout" can be used in this way, but the algorithms don't reflect this.
Comment 1 jleyba 2015-02-19 22:53:01 UTC
executeAsyncScript does reference timeout (step 1 in the algorithm in 10.3.1). Link to the timeout command needs to be updated though.