From c46a4ad1757f8cfc23c1c5096be8770e9e4baf97 Mon Sep 17 00:00:00 2001 From: Anne van Kesteren Date: Thu, 1 Sep 2016 09:57:14 +0200 Subject: [PATCH] Editorial: fix typo in public-script-coord spelling Fixes #322. --- dom.bs | 2 +- dom.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/dom.bs b/dom.bs index f697cebb6..634f1d585 100644 --- a/dom.bs +++ b/dom.bs @@ -1167,7 +1167,7 @@ of non-{{AddEventListenerOptions/passive}} listeners, and use that to clear the property of the event being dispatched.

Ideally, any new event APIs are defined such that they do not need this property (use -public-scrip-coord@w3.org +public-script-coord@w3.org for discussion). diff --git a/dom.html b/dom.html index 1bef5fe90..85318c3db 100644 --- a/dom.html +++ b/dom.html @@ -862,7 +862,7 @@

passive TouchEvent listeners must block scrolling, but if all listeners are passive then scrolling can be allowed to start in parallel by making the TouchEvent uncancelable (so that calls to preventDefault() are ignored). So code dispatching an event is able to observe the absence of non-passive listeners, and use that to clear the cancelable property of the event being dispatched.

-

Ideally, any new event APIs are defined such that they do not need this property (use public-scrip-coord@w3.org for discussion).

+

Ideally, any new event APIs are defined such that they do not need this property (use public-script-coord@w3.org for discussion).

3.8. Dispatching events

To dispatch an event to a target, with an optional targetOverride, run these steps: