- From: <bugzilla@jessica.w3.org>
- Date: Tue, 03 Feb 2015 16:46:25 +0000
- To: public-browser-tools-testing@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27950
Bug ID: 27950
Summary: executeScript and executeAsyncScript algorithms should
respect the script timeout
Product: Browser Test/Tools WG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: WebDriver
Assignee: public-browser-tools-testing@w3.org
Reporter: ato@mozilla.com
QA Contact: public-browser-tools-testing@w3.org
CC: mike@w3.org
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 3 February 2015 16:46:27 UTC