Revise DAS WG charter with a new deliverable proposed by Microsoft

[anssiko]

As discussed with key stakeholders.

[marcoscaceres]

Posting as W3C Member (not TAG Member).

This is an interesting capability worth exploring. The question is how it ended up here.

The CSS WG accepted haptics as a work item on March 31 (csswg-drafts#13728). Three weeks later it appears in the DAS charter. The PR description says "as discussed with key stakeholders," but doesn't say who these stakeholders are, where the discussion took place, or where the minutes are. How did this go from a CSS WG work item to a DAS charter deliverable?

There are also venue concerns. Haptics is not in the DAS WG's chartered scope (which covers: power status, screen/system sleep, nearby devices, ambient light, motion/orientation, and location). It is explicitly in the WebApps WG's scope ("Haptic input devices and their emitted events and/or data"). And the CSS WG is already working on the declarative side, with core open questions (triggering mechanisms, animation machinery, :snapped integration) that are CSS architecture problems.

Adding an out-of-scope deliverable to DAS while open charter issues (#780-#783) and the Vibration API scope question (#782, zero comments since March 31) remain unresolved compounds the problem.

Finally, the PR's "Adopted from WICG" and "Draft Community Group Report" are inaccurate: this work was presented to the CSS WG, not WICG, and the explainer describes itself as "early ideation."

[marcoscaceres]

Update: WICG/web-haptics was moved to WICG today, the day after this PR was filed. Haptics remains outside DAS's chartered scope, inside WebApps WG's scope, and already accepted as a work item by the CSS WG at their spring F2F. What's the intended coordination path across these venues?