You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: