Closed
Bug 1170581
Opened 9 years ago
Closed 9 years ago
Updating tab counter causes performance issues
Categories
(Firefox for iOS :: Home screen, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
fxios | + | --- |
People
(Reporter: sleroux, Assigned: sleroux)
References
Details
(Keywords: perf)
Attachments
(3 files)
Looks like the layoutIfNeeded call inside the updateTabCount is causing performance issues because it's relaying out all the subviews in order to calculate the cloned button's frame. A solution would be to statically set the button frame and not rely on the view to layout to determine the view's frame.
Assignee | ||
Comment 1•9 years ago
|
||
Assignee | ||
Updated•9 years ago
|
Flags: needinfo?(sleroux)
Assignee | ||
Comment 3•9 years ago
|
||
No it doesn't. Sorry not sure how that flag got turned on :/
Updated•9 years ago
|
Group: core-security
Updated•9 years ago
|
tracking-fxios:
--- → ?
Keywords: perf
Assignee | ||
Updated•9 years ago
|
Blocks: iosstartuptime
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → sleroux
Assignee | ||
Comment 4•9 years ago
|
||
Added some changes to improve the startup time of the app. Removed the layoutIfNeeded call when updating the tab count as it's not needed. Also removed the showToolbars call that was happening when the user selects a tab as the toolbars will always be shown if we are selecting a new tab and not calling it avoids a layout pass.
Attachment #8614165 -
Flags: review?(bnicholson)
Updated•9 years ago
|
Attachment #8614165 -
Flags: review?(bnicholson) → review+
Assignee | ||
Comment 5•9 years ago
|
||
Merged.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•