#1165: [wg/pointer-events] Pointer Events Working Group rechartering

Visit on Github.

Opened Nov 4, 2025

This issue was created because the 'horizontal review requested' label was added to § https://github.com/w3c/strategy/issues/515

This review is requested prior to the Advisory Committee Review.

New charter proposal, reviewers please take note.

Charter Review

Charter

diff from charter template

Expected end of charter refinement phase: unknown

If applicable:

diff from previous charter

chair dashboard

What kind of charter is this? Check the relevant box / remove irrelevant branches.

  • Existing
  • Existing WG recharter

Communities suggested for outreach

None. This is pure maintenance.

Known or potential areas of concern

Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...)

Raise issues

Anything else we should think about as we review?

Nope

cc @patrickhlauke

Charter facilitator(s)

cc @plehegar

<!-- Content below this is maintained by @w3c-tag-bot -->

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1165

Discussions

Comment by @martinthomson Dec 2, 2025 (See Github)

Thanks for the updated charter. We think that doing this sort of maintenance is an important task and there isn't anything in particular in the charter that looks problematic.

A few nits we noticed in reading this:

The link mentioned in the "Scope" section points to a list of exactly one issue: "see issues marked for future consideration in GitHub". Maybe consider doing something about that.

The scope also mentions that you plan to look at higher-level interfaces ("swipe left", "two finger tap"), but then the out of scope section that follows puts "higher-level APIs" out of scope. You can split hairs between the two, but it might be better to change the wording for those. I think that the first is "simplified events for common interactions", whereas the second is "APIs for interpreting abstract user intent via gestures". Or something along those lines.

You should also coordinate with the CSS WG when defining "new CSS touch-action values".