Closed Bug 1679204 Opened 3 years ago Closed 3 years ago

Consider to add signal to addEventListener


(Core :: DOM: Events, task)




86 Branch
Tracking Status
firefox86 --- fixed


(Reporter: smaug, Assigned: smaug)


(Keywords: dev-doc-complete)


(1 file)

This passes the tests which are in

Because of complications in #include handling, AbortFollower needs to be in a different
header file than AbortSignal, yet AbortSignalImpl needs to be available when AbortFollower is used.
Another option would have been to make DOMEventTargetHelper.h a bit different and uninline some hot methods
there or move them to another file, but that would have been equally bad and Abort* is used way less often.
AbortFollower and AbortSignalImpl are thus just moved to a new header.

Memory management is such that Listener in EventListenerManager owns the possible ListenerSignalFollower
instance which follows the relevant signal. In order to be able remove event listener,
ListenerSignalFollower has many similar fields as Listener.
ListenerSignalFollower can't easily have just a pointer to Listener* since Listener isn't stored as a pointer
in EventListenerManager.
ListenerSignalFollower cycle collectable so that Listener->ListenerSignalFollower can be traversed/unlinked
and also strong pointers in ListenerSignalFollower itself can be traversed/unlinked.

There is an XXX in the .webidl, since nullability of signal is unclear in the spec pr.
Whether or not it ends up being nullable shouldn't change the actual C++ implementation.

Severity: -- → N/A
Type: defect → task
Pushed by
Consider to add signal to addEventListener, r=edgar
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 86 Branch
Keywords: dev-doc-needed

The only information docs needed for this is BCD, which I am taking care of on

You need to log in before you can comment on or make changes to this bug.