Last Comment Bug 651984 - Add ability to detect if a page has registered touch event listeners
: Add ability to detect if a page has registered touch event listeners
: mobile
Product: Core
Classification: Components
Component: DOM: Events (show other bugs)
: unspecified
: All All
: -- normal (vote)
: mozilla6
Assigned To: Olli Pettay [:smaug]
: Andrew Overholt [:overholt]
Depends on: 648573
Blocks: 650342 654129
  Show dependency treegraph
Reported: 2011-04-21 15:02 PDT by Wesley Johnston (:wesj)
Modified: 2011-05-02 09:08 PDT (History)
1 user (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

patch (9.11 KB, patch)
2011-04-22 02:13 PDT, Olli Pettay [:smaug]
jst: review+
Details | Diff | Splinter Review

Description Wesley Johnston (:wesj) 2011-04-21 15:02:58 PDT
For Fennec, we need to dispatch touch events to content in the child process, and allow them to prevent us panning in the parent process. Unfortunately that introduces some lag between when the person beings dragging, and when we finally cancel panning in the parent process.

Alternatively, we can sacrifice some responsiveness in panning while we wait to see if the child cancels the event. However, we'd like to only do that when absolutely necessary, i.e. on pages that are actually using touch events.

To do so, we need some way to know when a page has registered a touch event listener, likely via a method added to nsIDOMWindowUtils?
Comment 1 Wesley Johnston (:wesj) 2011-04-21 15:03:21 PDT
Assigning to smaug by his request.
Comment 2 Olli Pettay [:smaug] 2011-04-22 02:13:49 PDT
Created attachment 527743 [details] [diff] [review]

I'm reusing the flag for MozTouch* events.
I expect MozTouch* events to be removed at some point.

The patch applies on top of Bug 648573
Comment 3 Johnny Stenback (:jst, 2011-04-25 15:15:47 PDT
Comment on attachment 527743 [details] [diff] [review]

Review of attachment 527743 [details] [diff] [review]:

Comment 4 Matt Brubeck (:mbrubeck) 2011-04-26 12:26:18 PDT

Note You need to log in before you can comment on or make changes to this bug.