#1256: [wg/immersive-web] Immersive Web WG 2026 Group Charter

Visit on Github

Opened Aug 7, 2026

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

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.

  • New
  • New WG
  • New IG
  • Existing
  • Existing WG recharter
  • Existing IG recharter

Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, security, and TAG. Also add a "card" for this issue to the Strategy Funnel.

Substantive changes

Short description (or link to it) of the substantive changes in this charter. Use "None or N/A" otherwise.

  • Adding new module (specification) but within current scope
  • (Still under investigation) Plan to bring modules to REC, while Core API remains living model in CR

Communities suggested for outreach

Known or potential areas of concern

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

Anything else we should think about as we review?

  • No CRS updated during current charter period yet.

Note: proposed chairs should be copied @... on this issue.

/cc @AdaRoseCannon @Yonet (co-chairs)

Note: The Technical Strategy Team Lead or Project & Process Team Lead will assign the issue to a Charter Facilitator for new charters. For rechartering, the team contact is the Charter Facilitator by default, please assign the issue to them directly.

Charter facilitator(s)

cc @himorin

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

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

Discussions

Log in to see TAG-private discussions.

Discussed Aug 17, 2026 (See Github)

Matthew: there were two architectural issues.

  1. around this idea of spatial CSS, and we discussed it last week. it's a big feature and they've clarified that they are going to work on that with the CSS WG, it will probably be a CSS WG deliverable, so the right people are working on this. I'm aware that Meta has a different proposal for doing similar stuff, and I asked about it but don't think I got a direct reply. I think Meta has people in CSS, and they'll probably sort that out themselves.

  2. High resolution haptics, speicifically in the context of game pads (but not just in game pads). that feels like something you'd want from any part of the platform, not just webXR. And that's the answer that I got.

A few other points on naming the APIs.

The answers we got were good thus far.

Luke: There is a participant from Meta in CSS, but I’m not sure if they are aware of that CSS proposal. Is this from Apple?

Matthew: I think so.

Hadley: Does it matter if there’s a competing proposal? Unless there’s a big impact on the web?

Luke: I think it might have such a big impact, also regarding privacy. Interop is a big part of the web architecture. Think Meta is a big player in immersive web. Would be unfortunate if people went down two different paths.

Matthew: +1, concern is if the conversations happened in the right places. Will ask ??? and maybe push a little more on the charter thread.

Hadley: There have been other occurrences where proposals were competing within the same working group. Also, policing the process is not our job. So, is it architectural? We’ll leave this to Luke and Matthew, and we respond next week?

Matthew: Ok.

Discussed Aug 31, 2026 (See Github)

Matthew: A couple of deliverables they listed I wanted to check that they are immersive-specific. One was higher resolution haptics for Gamepads.

… Left a comment on the charter on behalf of APA.

https://github.com/w3c/strategy/issues/564#issuecomment-5298679608 - questions 4 and 5 were the most potentially architectural

… Last one is a PCM thing I wanted to check. Don’t think it is WebXR-specific. They are developing use cases rather than a spec, and another group would do that. Another one is CSS Spatial Layout. There are at least two proposals for doing “spatial” as in depth. There’s an Apple proposal; Meta has a different approach to a similar problem. Wanted to make sure that this is being discussed. We need to make sure that people are aware this is being worked on. Need to send the link to Marcos.

Matthew to send the link to the #design-reviews Slack channel.

Comment by @bkardell Oct 5, 2026 (See Github)

Note there's a typo with closing tag

WebXR Mesh Detection Module The mesh detection API provides information about 3D surfaces detected in users' environment.

Draft state: Adopted from the Immersive Web CG

Expected completion: 2028 Q4/p>

Other than that, looks good to me. Propose we pass

Comment by @marcoscaceres Oct 6, 2026 (See Github)

I'm ok with pass... the only thing I was going to raise is about the gamepad PCM stuff being overly specific, but will talk to them about that during TPAC.