immersive-web / immersive-web/model-element
Specify fallback model for performance issues
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 86
- Forks
- 12
- Avg merge
- 7h 12m
- Merged PRs (30d)
- 1
Description
We should make sure the spec says something about the browser being able to drop the model on the floor if it's consuming too many resources or will make the user uncomfortable.
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 reviewing the specification text for the model element and the issue's discussion. Determine how the spec should describe browsers dropping a model when resource use could cause discomfort; completion requires an agreed, precise fallback requirement in the spec.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100