Closed Bug 684860 Opened 13 years ago Closed 12 years ago

Sluggish scrolling performance when scrolling through various UI panels

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox9 affected, fennec-)

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox9 --- affected
fennec - ---

People

(Reporter: aaronmt, Unassigned)

References

Details

(Keywords: meta, perf)

Device: Samsung Galaxy Tab 10.1 Build: Mozilla/5.0 (Android, Linux armv7l; rv:9.0a1) Gecko/20110906 Firefox/9.0a1 Fennec/9.0a1 Android: 3.1 When scrolling through All Pages, performance doesn't seem as fine tuned as it should be in comparison to other native applications (as well as in comparison to Fennec proper on my phone (Galaxy SII)).
Summary: Sluggish scrolling performance of results in Fennecomb awesomebar → Sluggish scrolling performance when cycling through results in Fennecomb awesomebar
Keywords: perf
Blocks: 680212
Re-summarizing bug title - this is affective on all panels, including scrolling through Add-Ons
Summary: Sluggish scrolling performance when cycling through results in Fennecomb awesomebar → Sluggish scrolling performance when scrolling through various UI panels
tracking-fennec: --- → ?
status-firefox9: --- → affected
Can you recheck this? Bug 686992 landed and should have improved the speed. If not, we have bug 657893 that could help too.
Tested on 09/29. Scrolling All Pages/Bookmarks/History seems a tad better. Scrolling through the list of available for download add-ons is still quite bad.
09/30, improved preferences; the add-on pane is better than before
Depends on: 657893
tracking-fennec: ? → +
Bug 657893 might help too, but that is based on GL.
Blocks: 459117
Depends on: 686992
Keywords: meta
Tracking '-' this bug is for the XUL UI.
tracking-fennec: + → -
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.