canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,798
edits
Mobile/Archive/PageInteractions: Difference between revisions
Jump to navigation
Jump to search
→Designs
MarkFinkle (talk | contribs) (Created page with '== Summary == Because of the panning behavior in Firefox Mobile, mousemove events are not dispatched to websites. That can break many popular web applications, like Google Maps,…') |
MarkFinkle (talk | contribs) |
||
| Line 26: | Line 26: | ||
Madhava, Stuart and Finkle talked through an initial design. The high points are: | Madhava, Stuart and Finkle talked through an initial design. The high points are: | ||
* Use " | * Use "getListenerInfoFor" to see if a content element wants to receive a mousemove event. If so, displatch it like we do for mousedown and mouseup. See http://mxr.mozilla.org/mozilla1.9.2/source/content/events/public/nsIEventListenerService.idl | ||
* If we are displatching mousemoves to the content, we need to create a finger-sized border area around the chrome window. Any touches the start in this border will _always_ start chrome panning and will _not_ be redispatched to content - no matter what. | * If we are displatching mousemoves to the content, we need to create a finger-sized border area around the chrome window. Any touches the start in this border will _always_ start chrome panning and will _not_ be redispatched to content - no matter what. | ||