- From: <bugzilla@jessica.w3.org>
- Date: Wed, 19 Mar 2014 23:35:27 +0000
- To: public-browser-tools-testing@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25100 Bug ID: 25100 Summary: [WebDriver Spec]: Change suggestion: include timeout parameter with executeAsyncScript Product: Browser Test/Tools WG Version: unspecified Hardware: All URL: https://dvcs.w3.org/hg/webdriver/raw-file/bafe03f45e86 /webdriver-spec.html#asynchronous-javascript-execution OS: All Status: NEW Severity: enhancement Priority: P2 Component: WebDriver Assignee: public-browser-tools-testing@w3.org Reporter: fisherii@google.com QA Contact: public-browser-tools-testing@w3.org CC: mike@w3.org Blocks: 20860 Rather than having a global timeout setting for async scripts, it might make things easier to include an optional timeout parameter. For many use cases of executeAsyncScript, I am basically forced to reset the async script timeout before every time I call it as it I don't necessarily know that it hasn't been reset by some other code (note, I am usually building testing infrastructure on top of WebDriver, not tests themselves). If I could include a timeout, this would allow me to set it for a particular call as needed and not have to worry about overriding the current default value, while saving me a WebDriver request. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 19 March 2014 23:35:29 UTC