Closed
Bug 724001
Opened 13 years ago
Closed 13 years ago
Performance of touch events is worse than stock browser
Categories
(Firefox for Android Graveyard :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: martijn.martijn, Assigned: wesj)
References
()
Details
(Keywords: perf)
See url testcase, when I try to make a circle in the canvas by drawing a circle motion, then that works fine in stock browser, but on current native Fennec trunk, I get more something like a hexagon.
It seems that Fennec really see that many touch move events as stock browser.
Assignee | ||
Comment 1•13 years ago
|
||
I have a feeling this has more to do with other factors outside the touch events code, but we need some profiling to find out.
Comment 2•13 years ago
|
||
martijn, can you try the same demo on Maple and see if it is better or not?
Priority: -- → P2
Reporter | ||
Comment 3•13 years ago
|
||
It seems that Maple fixes this (or mostly). I tested on the Samsung Galaxy Nexus and the HTC Desire HD. Compared it with the Aurora branch.
Assignee | ||
Comment 4•13 years ago
|
||
if we're fine with just saying "fixed in Maple" I can live with that. I was hoping to rewrite the testcase so that we didn't attempt to draw anything until touchend to make sure it wasn't painting that was affecting this. I have a feeling that we are coalescing touch and paint events here:
http://mxr.mozilla.org/mozilla-central/source/widget/android/nsAppShell.cpp#269
which kills us on things like this.
Updated•13 years ago
|
blocking-fennec1.0: --- → ?
Comment 5•13 years ago
|
||
wes, please nom if you think this should block fennec native.
Assignee: nobody → wjohnston
blocking-fennec1.0: ? → ---
Comment 6•13 years ago
|
||
There have been many speedups done to touch events. I just tested this again on the GN and it seems pretty smooth. Going to mark as WFM.
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•