1500631 - Consider removing document.createTouch and document.createTouchList

Status: NEW

(Core :: DOM: Events, task, P3)

Description

[Andrew McCreight [:mccr8]]

Chrome dropped this in May: https://github.com/web-platform-tests/wpt/commit/8e1adf3ff681a013968a3fd6b3115c44587babec https://github.com/web-platform-tests/wpt/commit/6a23e9de469476253e59744a2635d3574bc33e1d

This leaves Firefox as the only browser that implement them, it seems.

Comment 1

[Olli Pettay [:smaug][[e-mail]]]

Yeah, I think we should try to remove them.

Comment 2

[Olli Pettay [:smaug][[e-mail]]]

or, possibly enable them only if some pref is set, so that tests can still utilize those.

Comment 3

[Olli Pettay [:smaug][[e-mail]]]

Marionette seems to use createTouchList. Could it use something else?
We have synthesizeTouch etc. in EventUtils.js

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2]]

This is only used by the old actions API implemented in Marionette and which we want to get rid of via bug 1354578. It's actually something we want to get rid of for a while. So lets see if we can make it somewhat a priority. If you have more questions lets continue over there.

Comment 5

[Kagami Rosylight [:saschanaz] (they/them)]

Bug 1412485 in 2019 limited this to Android with dom.w3c_touch_events.legacy_apis.enabled. (Chrome doesn't have it on Android either, so keeping parity-chrome.)