From d088d6e5c394c3d689e3b5a12615848e5a7b8bfa Mon Sep 17 00:00:00 2001 From: Deokjin Kim Date: Thu, 12 Jan 2023 01:29:53 +0900 Subject: [PATCH] events: change status of `event.cancelBubble` to legacy `event.cancelBubble` is described as legacy in spec. Refs: https://dom.spec.whatwg.org/#interface-event PR-URL: https://github.com/nodejs/node/pull/46146 Reviewed-By: Yagiz Nizipli Reviewed-By: Antoine du Hamel Reviewed-By: Anna Henningsen --- doc/api/events.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/api/events.md b/doc/api/events.md index 39d23ffb3abf66..b53c6a6bacaf11 100644 --- a/doc/api/events.md +++ b/doc/api/events.md @@ -1754,6 +1754,8 @@ This is not used in Node.js and is provided purely for completeness. added: v14.5.0 --> +> Stability: 3 - Legacy: Use [`event.stopPropagation()`][] instead. + * Type: {boolean} Alias for `event.stopPropagation()` if set to `true`. This is not used @@ -2162,6 +2164,7 @@ to the `EventTarget`. [`emitter.listenerCount()`]: #emitterlistenercounteventname [`emitter.removeListener()`]: #emitterremovelistenereventname-listener [`emitter.setMaxListeners(n)`]: #emittersetmaxlistenersn +[`event.stopPropagation()`]: #eventstoppropagation [`event.target`]: #eventtarget [`events.defaultMaxListeners`]: #eventsdefaultmaxlisteners [`fs.ReadStream`]: fs.md#class-fsreadstream