From 17446356e9a22164795bb39aab4ca4daec58205d Mon Sep 17 00:00:00 2001 From: Dominique Hazael-Massieux Date: Wed, 17 Apr 2024 14:29:38 +0200 Subject: [PATCH] Complete machine-readable scope of and event dfns The summary table correctly lists `CloseWatcher` (for `cancel` and `close`) and `MessagePort` (for `close`) as target interfaces for the event, but these interfaces are missing from the machine-readable `for` attribute. Via https://github.com/w3c/webref/issues/1212#issuecomment-2058852721 --- source | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source b/source index aa0fb43a5e2..94eaad8f7b6 100644 --- a/source +++ b/source @@ -141878,7 +141878,7 @@ INSERT INTERFACES HERE Fired at nodes when they stop being focused - cancel + cancel Event CloseWatcher, dialog elements, input elements Fired at CloseWatcher objects or dialog elements when they receive a close request, or at input elements in the File state when the user does not change their selection @@ -141896,7 +141896,7 @@ INSERT INTERFACES HERE Normally a mouse event; also synthetically fired at an element before its activation behavior is run, when an element is activated from a non-pointer input device (e.g. a keyboard) - close + close Event CloseWatcher, dialog elements, MessagePort Fired at CloseWatcher objects or dialog elements when they are closed via a close request or via web developer code, or at MessagePort objects when disentangled