- From: Simon Pieters <notifications@github.com>
- Date: Tue, 03 May 2022 09:03:30 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 3 May 2022 16:03:42 UTC
> Does this close #952? Yes. > What about https://bugzilla.mozilla.org/show_bug.cgi?id=1693172? Hmm. I thought Firefox exposed `window.TouchEvent`, since it passes the relevant test in https://wpt.fyi/results/touch-events/idlharness.window.html?label=experimental&label=master&aligned But running the test locally on macOS desktop Firefox it's not exposed. Maybe it's a difference between Linux and macOS? In any case, we should indeed make a decision whether `window.TouchEvent` should exist when "expose legacy touch event APIs" is false. What's specified now in the touch events spec + this PR matches Chromium, but seemingly not Safari or Firefox. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/pull/1071#issuecomment-1116269181 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/pull/1071/c1116269181@github.com>
Received on Tuesday, 3 May 2022 16:03:42 UTC