Open Bug 1432169 Opened 7 years ago Updated 2 years ago

Consider firing ViewShowing events before moving the "panelview" node

Categories

(Firefox :: Toolbars and Customization, enhancement, P5)

Product:
Firefox
Component:
Toolbars and Customization
Type:
enhancement

Tracking

()

Project Flags:
Performance Impact low
Tracking Flags:
Tracking Status
firefox59 --- affected

People

(Reporter: Paolo, Unassigned)

Details

(Keywords: perf:frontend, perf:responsiveness, Whiteboard: [triage]) 

Since a <panelview> node may be moved again later for asynchronous layout, we may be able to improve performance by auditing the "ViewShowing" handlers to check they don't rely on the assumption that the new <panelview> is a descendant of <panelmultiview>, and fire the event before moving it. We would need to fire the "ViewShowing" event separately on the <panelmultiview> element when it is not an ancestor already.

This is probably a low priority enhancement, as this may happen often only for the Library subview, and has likely a low impact even for users that switch frequently between the two menus.
Priority: -- → P5
Whiteboard: [fx-perf][triage] → [fxperf][triage]
Whiteboard: [fxperf][triage] → [fxperf:p3][triage]
Severity: normal → S3
Performance Impact: --- → low
Keywords: perf:frontend, perf:responsiveness
Whiteboard: [fxperf:p3][triage] → [triage]
You need to log in before you can comment on or make changes to this bug.