Closed Bug 559651 Opened 10 years ago Closed 10 years ago
There is no need for an EventInfo wrapper. The only additional property it adds was the time of the generated event.
Updated on trunk and really remove only the EventInfo code (and where it is used)
Comment on attachment 458329 [details] [diff] [review] Patch v0.2 >diff -r 36723271befb chrome/content/InputHandler.js >+ aEvent.time = Date.now(); Do we even use "time" anywhere? MXR says we don't
Attachment #458329 - Flags: review?(mark.finkle) → review+
(In reply to comment #2) > Comment on attachment 458329 [details] [diff] [review] > Patch v0.2 > > >diff -r 36723271befb chrome/content/InputHandler.js > >+ aEvent.time = Date.now(); > > Do we even use "time" anywhere? > > MXR says we don't yep we do: http://mxr.mozilla.org/mobile-browser/source/chrome/content/InputHandler.js#644 http://hg.mozilla.org/mobile-browser/rev/d39aff00f0f5
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.