-
Notifications
You must be signed in to change notification settings - Fork 11
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
Adding "controls" #43
Comments
Maybe this can be added in the later level of the spec? Also, afaik almost no sites use the built-in video controls |
Sorry, could you elaborate what you mean by "the user making changes"? Also, how would it differ from, say,
I agree that well-resourced sites should absolutely have the ability to add their own controls. However, as with video/audio, there are significant advantages usability, accessibility, robustness, and just ease of use to not requiring scripting for controls (i.e. to the user agent providing them... whatever they may be...). It's also highly future proof, with the user agent being able to add device-specific controls as new capabilities become available to the user agent. Personally speaking, when embedding videos on page, I've always relied on the browser to provide me with controls. test.mov |
A 3D model can have more than one animation. For example a game character can include walking, running and jumping animations. The controls ui would then need to include a drop down to select the animation to play. |
Safari on iPhone, as far as I know, always displays native video controls in full-screen web
I suspect that any user agent that does this to video content would also would apply the same principles to 3D-model content. |
@mrdoob wrote:
Could definitely be in option. However, that might not work well unless the camera also moved to the right position so the user could view the animation. Speaking hypotheticals here: I was thinking more if the format defined a "top-level" (or scene-level?) animation. |
Actually if we're talking about 3D controls in terms of accessibility having directional buttons to tumble a model and + and - to zoom in and out is ideal for some users. So outside of animation control there may be other controls that need to be investigated. ASFAIK the built in |
Right, but they are not mutually exclusive. You still want a minimal set of controls (or potentially a specialized set of controls) for some users, while being privacy preserving. Sites can still offer a rich set of HTML based controls, but some users should still be able to enable UA-provided controls should they desire or need them (or they simply choose to disable JS). |
Agreed. I've found the minimal controls in videos to be valuable. Especially as a developer having the ability to test playback immediately is awesome. |
I'm not sure if this totally the right thread but I can imagine users also
wanting to attach a rotation to the scroll timeline such as when you scroll
it rotates from the top view and then moves to the bottom
This may have interesting interactions with rotation controls
…On Wed, 10 Aug 2022, 19:43 Mikko Haapoja, ***@***.***> wrote:
Agreed. I've found the minimal controls in videos to be valuable.
Especially as a developer having the ability to test playback immediately
is awesome.
—
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAHSMT4HJGTN33GCTQ37VLVYPZ6HANCNFSM55Q6K63A>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
As with other media elements (again #13), having "controls" for media specific things can be extremely helpful for accessibility (and just generally helpful for developers not needing to deal with things like the fullscreen API).
It would be nice to consider adding support for
controls
and then leaving it mostly to the UA as to what those controls are... we could figure out a standard set of things, like<video>
provides.The text was updated successfully, but these errors were encountered: