Closed Bug 815115 Opened 12 years ago Closed 10 years ago

[B2G] Make Marionette touch events synchronous or take a condition to wait for

Categories

(Remote Protocol :: Marionette, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: davehunt, Unassigned)

References

Details

The dialer test needs to use long_touch on the zero button to enter a '+', and currently this call is asynchronous. This means the test must either include a sleep at least equal to the duration of the touch event, or an additional wait must be used. If using a wait, and this completes before the long touch duration, then an additional '0' appears in the phone number.

I would suggest either making these methods synchronous according to the delay passed to them, or allowing a condition to be passed to them so the event only lasts until the condition is met.
Severity: normal → major
Depends on: 816246
No longer depends on: 815361
Assignee: nobody → dburns
resetting this just for now
Assignee: dburns → nobody
Now that we're moving away from the touch mixin, this synchronous return will have to occur in Marionette itself. It might be worth investigating. It should be possible to return after the last event gets dispatched by adding an event handler to the window for the last event, and return to the client once the event's id/coordinates match the id/coordinates of the the last touch event we're dispatching. 

Dburns, what do you think of this approach of returning once the last event is successfully received on the page for webdriver in general?
Severity: major → critical
Severity: critical → normal
Malini: I believe this can now be achieved using action chains?
Flags: needinfo?(mdas)
Yes, thanks for commenting, I'll mark this as won't fix, since the problem was solved in a different way.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(mdas)
Resolution: --- → WONTFIX
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.