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
I'm thrilled that we have the explainer text approved! The next step is what people need out of a spec - My understanding is that specification text is at a level of granularity that implies certain things about implementation.
Since I'm not personally implementing, I don't know when folks need to get into more granular language or how detailed it gets in the spec. For reference, here are some of the main moving parts for <model> that spring to mind:
There's not a great code search for play/pause/playbackRate etc but it's exposed like a media element
(per discussion at TPAC it's not media element but we might be able to bridge the spec somehow)
/agenda what does anyone need in spec-land right now that isn't being addressed by the explainer?
The text was updated successfully, but these errors were encountered:
I'm thrilled that we have the explainer text approved! The next step is what people need out of a spec - My understanding is that specification text is at a level of granularity that implies certain things about implementation.
Since I'm not personally implementing, I don't know when folks need to get into more granular language or how detailed it gets in the spec. For reference, here are some of the main moving parts for
<model>
that spring to mind:Getting and setting the view/entity transform
Exposing Bounding box information
Setting/updating environmentmap
There's not a great code search for play/pause/playbackRate etc but it's exposed like a media element
(per discussion at TPAC it's not media element but we might be able to bridge the spec somehow)
/agenda what does anyone need in spec-land right now that isn't being addressed by the explainer?
The text was updated successfully, but these errors were encountered: