immersive-web / immersive-web/layers
Define how input is handled
Open
Nobody has claimed this yet.
Future enhancement
- Dominant language
- HTML
- Stars
- 96
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Only the UA really knows where layers are placed in 3D space.
The author (or JS framework) can guess where they are but this might be brittle.
What is the best way to provide input events? Should non-projection layers become event targets?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the issue's questions about input events, 3D layer placement, and whether non-projection layers should be event targets. Review the surrounding WebXR Layers design discussion and establish a resolved behavior for authors and JavaScript frameworks. Done means the input-handling rules are clearly specified and the event-target behavior is settled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100