Closed Bug 619824 Opened 14 years ago Closed 14 years ago

Dispatch a delayed mousemove event soon after TapDown

Categories

(Firefox for Android Graveyard :: General, defect)

defect
Not set
normal

Tracking

(fennec2.0+)

VERIFIED FIXED
Tracking Status
fennec 2.0+ ---

People

(Reporter: vingtetun, Assigned: vingtetun)

References

Details

Attachments

(1 file)

Attached patch PatchSplinter Review
Now that Electrolysis is in place we could safely dispatch a mousemove event soon after TapDown without fearing to regress panning, in fact this also fix a regression because before e10s we were doing delayed highlighting...
Attachment #498241 - Flags: review?(mark.finkle)
tracking-fennec: --- → 2.0+
Comment on attachment 498241 [details] [diff] [review]
Patch


>diff --git a/chrome/content/input.js b/chrome/content/input.js

>+      this._mouseoverTimeout.once(kOverTapWait);

this._mouseOverTimeout.once(kOverTapWait);

>+  _doMouseover: function _doMouseover() {

_doMouseOver:
Attachment #498241 - Flags: review?(mark.finkle) → review+
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Any automated tests or ways to verify this?
(In reply to comment #4)
> Any automated tests or ways to verify this?

I guess a browser-chrome test would be nice for it. I will do one in a few.
Depends on: 623763
How can I verify this?
Verified - when clicking on https://bug460966.bugzilla.mozilla.org/attachment.cgi?id=344091 the sub menu appears while your finger is down where as on a build before Dec-16th the menu shows when your finger leaves the screen

Mozilla/5.0 (Android; Linux armv7l; rv:7.0a1) Gecko/20110527 Firefox/7.0a1 Fennec/7.0a1 ID:20110527031218
Status: RESOLVED → VERIFIED
bugspam
Assignee: nobody → 21
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: