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 25318 - It's not clear why wait is nullable and optional
Summary: It's not clear why wait is nullable and optional
Status: RESOLVED INVALID
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: 20860
  Show dependency tree / graph
 
Reported: 2014-04-10 21:33 UTC by Andrey Botalov
Modified: 2015-10-26 03:01 UTC (History)
2 users (show)

See Also:

Attachments

Description Andrey Botalov 2014-04-10 21:33:31 UTC 
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.
Comment 1 David Burns :automatedtester 2014-04-22 22:37:25 UTC 
at the last face to face it was decided that we needed an image to describe this, at least until we could get prose that could describe the intent clearly
Comment 2 David Burns :automatedtester 2015-10-26 03:01:01 UTC 
not need worry about this anymore