- From: Simon Pieters <notifications@github.com>
- Date: Tue, 03 May 2022 10:51:27 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 3 May 2022 17:51:38 UTC
Gecko seems to have two levels of API exposure: - `dom_w3c_touch_events_enabled` (set to 0 on macOS, 1 on Android and autodetect on some platforms) - `dom_w3c_touch_events_legacy_apis_enabled` (affects `createEvent` and `ontouch*` handlers) References - https://searchfox.org/mozilla-central/source/modules/libpref/init/StaticPrefList.yaml#4081-4092 - https://searchfox.org/mozilla-central/search?q=StaticPrefs%3A%3Adom_w3c_touch_events_enabled%28%29&path= - https://searchfox.org/mozilla-central/search?q=dom_w3c_touch_events_legacy_apis_enabled&redirect=false - https://searchfox.org/mozilla-central/source/dom/events/EventDispatcher.cpp#1361 - https://searchfox.org/mozilla-central/source/dom/webidl/HTMLElement.webidl#96 So I think Gecko matches Chromium when `dom_w3c_touch_events_enabled` is 1 (or autodetected as enabled). -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/952#issuecomment-1116380371 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/952/1116380371@github.com>
Received on Tuesday, 3 May 2022 17:51:38 UTC