Closed
Bug 861772
Opened 11 years ago
Closed 3 years ago
TouchAdapter.jsm shouldn't use "mouseenter" and "mouseleave"
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
INVALID
People
(Reporter: masayuki, Assigned: eeejay)
References
Details
(Keywords: perf, regression)
http://mxr.mozilla.org/mozilla-central/source/accessible/src/jsat/TouchAdapter.jsm#66 mouseenter and mouseleave events shouldn't be used in chrome since adding listeners for them makes damage to the performance on the document.
|
||
Comment 1•11 years ago
|
||
Is this for Firefox OS or for Firefox for Android?
|
Reporter | |
Comment 2•11 years ago
|
||
I don't know. Anyway, we need to avoid using them in chrome because if they're listened, nsEventStateManager needs to dispatch much a lot of those events. https://developer.mozilla.org/ja/docs/DOM/DOM_event_reference/mouseenter
|
||
Updated•9 years ago
|
Summary: TouchAdapter.jsm shouldn't use "mosueenter" and "mouseleave" → TouchAdapter.jsm shouldn't use "mouseenter" and "mouseleave"
|
||
Comment 3•3 years ago
|
||
TouchAdapter no longer exists, since AccessFu is gone and we don't handle touch directly any more on Android.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•