immersive-web / immersive-web/model-element
Limitations on playback - user gestures, preferences etc
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 86
- Forks
- 12
- Avg merge
- 7h 12m
- Merged PRs (30d)
- 1
Description
Media elements often require a user gesture for playback - either directly, or through the chain of input that ultimately results in the playback.
Playback can also be limited based on things like user configuration, reduced motion or battery levels (though I'm not sure which of these are mandatory versus optionally being disabled per-site by conscientious developers.)
I don't believe we have currently established any requirements for when programmatic playback should be prevented - is there a standard template to follow? Do we think that the video playback case is enough to copy verbatim?
/agenda
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 with the issue's questions about user gestures, user configuration, reduced motion, battery levels, and programmatic playback, then compare the video playback case it references. Resolve which restrictions are mandatory and whether a standard template should be followed; the issue names no file or test, and completion would require agreed requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100