If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Consider not observing mutations in nsContentList when it is dirty

UNCONFIRMED
Unassigned

Status

()

Core
DOM
P2
normal
UNCONFIRMED
3 months ago
3 months ago

People

(Reporter: smaug, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 months ago
Right now nsContentList adds itself as an nsIMutationObserver in ctor and removes in dtor, meaning that even if list is dirty and returns early in mutation observing methods, there are always some virtual calls and state checks.
Not observing would mean that mRootNode should probably need to become strong ref.

Updated

3 months ago
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.