From 1c9532bf9a52bc548ce3ea0cb6de025e4f6a7537 Mon Sep 17 00:00:00 2001 From: "Daniel D. Beck" Date: Tue, 10 Dec 2024 16:49:10 +0100 Subject: [PATCH] Revise `event` description to make it clear that it's generic This is one of those foundational features that's both difficult to avoid and hard to make explicit inside our length constraints. --- features/events.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/features/events.yml b/features/events.yml index dcc84fc808d..b45e5164f5e 100644 --- a/features/events.yml +++ b/features/events.yml @@ -1,5 +1,5 @@ name: Events -description: Events fire when significant things happen in the page, such as an image loading or a user clicking. You can use the `addEventListener()` method on objects that receive events (event targets), such as windows, documents, and elements, to set a function to be called when an event fires. +description: The `Event` API and the `addEventListener()` method on objects that receive events (event targets) represent and handle significant things happening on a page. Many APIs fire events for a wide range of situations relating to those APIs, such as an image loading, a user clicking, or a value changing. spec: - https://html.spec.whatwg.org/multipage/indices.html#events-2 - https://dom.spec.whatwg.org/#interface-customevent