709469 - [Gonk] Consider postMessage() instead of setTimeout(..., 0) to dispatch click events

Status: RESOLVED WONTFIX

(Core :: General, defect)

Description

[Philipp von Weitershausen [:philikon]]

Currently touch.js uses setTimeout(..., 0) to ensure click event handlers don't block the click event dispatch. However, there's a delay of a few ms associated with it. gal suggested in bug 708538 to use postMessage instead.

(Note that postMessage can be pretty allocation heavy since it creates new event objects and marshals the data that's transferred.)

Comment 1

[Tim Guan-tin Chien [:timdream] (please needinfo)]

Alternately would be use the setImmediate proposed by IE guys.

https://developer.mozilla.org/en/DOM/window.setImmediate

Since these no setImmediate in Gecko, we can use this *and* then shim it. I have code to recycle from that does this.

Comment 2

[[:fabrice] Fabrice Desré]

This is chrome land code, so we really don't wont shims there. postMessage() seems to be the way to go.

Comment 3

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

What about the schedule API that is proposed in bug 692420?

Comment 4

[Philipp von Weitershausen [:philikon]]

(In reply to Vivien Nicolas (:vingtetun) from comment #3)
> What about the schedule API that is proposed in bug 692420?

Sure. But touch.js is chrome code, right? Just do

   Services.tm.currentThread.dispatch(func, Ci.nsIThread.DISPATCH_NORMAL);

Comment 5

[Sylvestre Ledru [:Sylvestre]]

Closing as we are not working on Firefox OS anymore.