- From: <bugzilla@jessica.w3.org>
- Date: Thu, 10 Apr 2014 21:33:31 +0000
- To: public-browser-tools-testing@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25318 Bug ID: 25318 Summary: It's not clear why wait is nullable and optional 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: botalov.andrey@gmail.com QA Contact: public-browser-tools-testing@w3.org CC: mike@w3.org Documentation for "wait" in touch gestures API says that wait "defaults to zero so that it can be used for synchronising actions". But it's not clear to me how "wait(0)" can synchronize anything as it will be processed ~0 milliseconds and thus won't be able to synchronize. I think wait should be neither nullable nor optional. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 10 April 2014 21:33:32 UTC