Stop calling _mouseleave and _mouseenter from _setPositionalAttributes
Categories
(Firefox :: Tabbed Browser, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox110 | --- | fixed |
People
(Reporter: Oriol, Assigned: Oriol)
References
(Blocks 1 open bug)
Details
(Keywords: perf:frontend)
Attachments
(1 file)
The main reason for calling _mouseleave and _mouseenter from _setPositionalAttributes was to update the beforehovered and afterhovered attributes, as the tabs these attributes were set on might change.
However, bug 1808661 is removing these attributes, so mouseenter and mouseleave events should be sufficient for updating _hoveredTab itself.
_setPositionalAttributes is a hot code-path, so avoiding the expensive querySelector("tab:hover") will improve performance.
| Assignee | ||
Comment 1•3 years ago
|
||
Calling _mouseleave and _mouseenter from _setPositionalAttributes used
to be needed to update the beforehovered and afterhovered attributes,
as the tabs these attributes were set on might have changed.
However, bug 1808661 removed these attributes, so mouseenter/mouseleave
events should be sufficient for updating _hoveredTab itself.
_setPositionalAttributes is a hot code-path, so avoiding the expensive
querySelector("tab:hover") will improve performance when having lots of
tabs.
Depends on D166094
Comment 3•3 years ago
|
||
| bugherder | ||
Updated•3 years ago
|
Description
•