emulation.setMaxTouchPoints

[sadym-chromium]

The hook is supposed to be used in navigator.maxTouchPoints and in "expose legacy touch event APIs".

Addressing #1028.

• Pointer Events spec PR: WebDriver BiDi emulated max touch points pointerevents#561
• Mention legacy Touch Events - Level 2 in the note.

Open questions:

• Should the command name be more generic?

---

Preview | Diff

[css-meeting-bot]

The Browser Testing and Tools Working Group just discussed `emulation.setMaxTouchPoints` invokes legacy archived specification, and agreed to the following:

• ACTION: jdescottes to follow up on this [1]

The full IRC log of that discussion

<AutomatedTester> topic: `emulation.setMaxTouchPoints` invokes legacy archived specification
<AutomatedTester> github: https://github.com//pull/1042
<AutomatedTester> sadym: this is a step forward for mobile emulation, please can people review
<AutomatedTester> jgraham: pointer events does this and we shouldn't be referencing touch events is a not a good idea. I haven't read the PR
<AutomatedTester> ... if we are using legacy APIs we should suggest to people to use a non-legacy API for things
<jgraham> s/should suggest people use a non-legacy API for things/just have a non-normative note about what implementations implementing those nonstandard APIS might want to do, because all the behaviour here is nonstandard anyway/
<jgraham> RRSAgent: make minutes
<RRSAgent> I have made the request to generate https://www.w3.org/2025/12/10-webdriver-minutes.html jgraham
<jgraham> Zakim, bye
<Zakim> leaving. As of this point the attendees have been AutomatedTester, jimevans, jdescottes, tidoust, whimboo, orkon, jgraham, sasha, sadym, bburg
<jgraham> RRSAgent: make minutes
<RRSAgent> I have made the request to generate https://www.w3.org/2025/12/10-webdriver-minutes.html jgraham
<jgraham> RRSAgent: bye
<RRSAgent> I see 1 open action item saved in https://www.w3.org/2025/12/10-webdriver-actions.rdf :
<RRSAgent> ACTION: jdescottes to follow up on this [1]
<RRSAgent> recorded in https://www.w3.org/2025/12/10-webdriver-irc#T17-49-34
<jdescottes> sadym for info, still planning to cleanup the fetch PRs. If you have any concern around https://github.com//issues/722#issuecomment-3615679079 let me know. If not I'll move forward with the current plan mentioned in the issue.

[OrKoN]

I would be in favor of renaming to emulation.setTouchOverride or similar. I wonder what others think.