1. Load any bugzilla bug page (such as this one) 2. Click anywhere on the page (for example on the empty space to the right of the comments --->) Expected results: - no haptic feedback Actual results: - haptic feedback This is happening because the root HTMLDocument has a mouse listener registered on it, so we determine that it is "clickable" and therefore every element on the page is also "clickable". I don't know if there's a good solution to this problem, but maybe don't do haptic feedback for mouse listeners beyond a certain height in the DOM tree (i.e. body or root nodes)? Requesting nom for 1.0. This bug in itself isn't so bad, but it adds to confusion for issues like bug 751200 and bug 735539.

We should only provide haptic feedback when tapping near "clickable" form controls/links

I'm not sure what that means, or that we want to do it if it means what I think. I don't want to filter out things like div's, spans, lis, etc that are other used for "button" like stuff. But I'd be fine with filtering out body and maybe canvas?

Talked to mfinkle. We already only fire this on clickable things: http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/browser.js#2651 Body is clickable on bugzilla. I'm fine WONTFXing.

(In reply to Wesley Johnston (:wesj) from comment #3) > Body is clickable on bugzilla. I'm fine WONTFXing. Me too. We check for elements with click handlers. If the entire body is a click target, we need to give haptic feedback. If we still want to "correct" this issue, file a bug on bugzilla to remove the body click handler.