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 25317 - Touch gestures API marks some high-level methods as low level one
Summary: Touch gestures API marks some high-level methods as low level one
Status: RESOLVED FIXED
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 treegraph
 
Reported: 2014-04-10 21:27 UTC by Andrey Botalov
Modified: 2015-10-26 02:41 UTC (History)
2 users (show)

See Also:


Attachments

Description Andrey Botalov 2014-04-10 21:27:01 UTC
Theoretically the following methods are low level methods as it's theoretically possible to implement all other touch methods using those methods:
void press (WebElement id, optional Long x, optional Long y);
void moveTo (WebElement id, optional Long x, optional Long y);
void release ();
void wait (optional number? ms);

"tap" can theoretically be implemented as "press" + short "wait" depending on device + "release"
"longPress" - "press" + longer "wait" depending on device + "release"

I don't see a point of "cancel" as it's not something that a user can do with touch screen. User can remove his finger from touch screen/lock device/touch screen using another finger. He can't "cancel".

Of course that makes sense only from theoretical point of view but "click" is also not a combination of low level methods if native events are turned off.
Comment 1 David Burns :automatedtester 2015-10-26 02:41:05 UTC
This has been corrected in 12.3