Closed
Bug 464129
Opened 16 years ago
Closed 16 years ago
autocomplete measurement
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: taras.mozilla, Unassigned)
References
Details
No description provided.
|
Reporter | |
Comment 2•16 years ago
|
||
First,there is invisible autocomplete slowdown that causes typing lag
For example, i click on titlebar, hit backspace. Then for every letter i type in
about 20 setTimeouts of _setUpOverflow ( http://mxr.mozilla.org/mozilla-central/source/toolkit/content/widgets/autocomplete.xml#1458 ) are called each takes 7-15ms, sometimes more. This causes a second of more of cursor lag when typing into location bug.
As far I can tell end result of that function is usually nothing.
|
|
Reporter | |
Comment 3•16 years ago
|
||
Updating searchengines on first autocomplete display takes 750ms on first run,
+15ms(barely above noise) to show the popup. This is just js overhead. I don't have a way to measure layout costs.
|
|
Reporter | |
Comment 4•16 years ago
|
||
gavin changed autocomplete so this no longer applies
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
|
||
Comment 5•15 years ago
|
||
autocomplete is disabled on builds:
Mozilla/5.0 (X11; U; Linux armv6l; en-US; rv:1.9.2b1pre) Gecko/20091002
Fennec/1.0b4
and
Mozilla/5.0 (X11; U; Linux armv7l; en-US; rv:1.9.2b1pre) Gecko/200910002
Fennec/1.0b4
Status: RESOLVED → VERIFIED
sorry for bug spam.
Many of the bugs which are marked invalid, I see comments telling it occurred in one version or other. But later it was fixed due to 1) by backingout the patch which made regression or 2) by fixing some other bug.
So if we can identify the bug/patch/reason then we should state that and mark those as FIXED. If not mark as WORKSFORME in that case.
You need to log in
before you can comment on or make changes to this bug.
Description
•