- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 06 Jan 2025 04:54:36 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 6 January 2025 12:54:40 UTC
I don't think Chrome is following the specification here. While the callback is the same, the listener is not (we create a new listener for each call to `addEventListener()`). And it's the listener that we attempt to remove. Firefox and Safari handle this correctly. Nice discovery though! We should add test coverage for this. I think we probably don't want to add steps to clean up the signal's abort algorithms as it's not observable and would add some amount of complexity. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/1346#issuecomment-2573054252 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/1346/2573054252@github.com>
Received on Monday, 6 January 2025 12:54:40 UTC