+++ This bug was initially created as a clone of Bug #774458 +++ Split this off for follow up work. This is likely too risky for B2Gv1, but we should do it sometime to make sure we're providing consistent events across browsers. We're still sending mouse events from: http://mxr.mozilla.org/mozilla-central/source/widget/gonk/nsAppShell.cpp#438 Android does something similar to support XUL Fennec (which required mouse events), but uses a flag to turn it off in Native Fennec: http://mxr.mozilla.org/mozilla-central/source/widget/android/nsWindow.cpp#1173 > Comment 23 Michael Wu [:mwu] 2012-12-06 14:28:31 PST > We'll need a new bug to fix this issue in non-async scroll content but the risk vs. > reward there doesn't seem to be right. A lot of gaia would break. I looked at just > killing mouse events on webapps, but there's also no evidence so far that adding mouse > events would improve compatibility. It seems like webapps largely just check useragents > to determine whether touch events can be used.
Note: bug 823619 changed this for app content, which is what we care about. The mouse events dispatched by the gonk widget backed go to hacky code we were forced to run in-process in b2g v1. If all goes well, those deficiencies will be lifted in v2 and we don't have to worry about this. But at any rate, 823619 supplies about 4/5ths of the fix to this.
This was fixed a long time ago.