Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify fallback model for performance issues #68

Open
marcoscaceres opened this issue Aug 14, 2023 · 2 comments
Open

Specify fallback model for performance issues #68

marcoscaceres opened this issue Aug 14, 2023 · 2 comments

Comments

@marcoscaceres
Copy link
Contributor

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.

@DR-xR
Copy link

DR-xR commented Aug 15, 2023

The browser should really fail gracefully. Dropping it on the floor, especially without warning or notice, can be bad too.

@cabanier
Copy link
Member

During the meeting, people mentioned that browser currently don't specify what happens when images are too big or if there are too many so we don't need to do anything.
However, the model tag is different because a lot of existing content will not be renderable at a acceptable frame rate by existing and near future headsets. We should require that there is a image fallback in the element in case the model is too big or not renderable or if there are too many.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants