Event listeners are created and sometimes not removed. This leads to memory leaks.
This happens when isCaptureMode is true, since removeEventListener needs the same useCapture flag as used in addEventListener.
Possible fixes include:
- calling
removeEventListener twice with true and false for useCapture.
- storing the
useCapture value used by addEventListener and using it when calling removeEventListener.
- providing
currentTarget to determine isCaptureMode when calling removeEventListener.
Event listeners are created and sometimes not removed. This leads to memory leaks.
This happens when
isCaptureModeis true, sinceremoveEventListenerneeds the sameuseCaptureflag as used inaddEventListener.Possible fixes include:
removeEventListenertwice withtrueandfalseforuseCapture.useCapturevalue used byaddEventListenerand using it when callingremoveEventListener.currentTargetto determineisCaptureModewhen callingremoveEventListener.