-
Notifications
You must be signed in to change notification settings - Fork 12
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
Capability: Toggle whether default controls are displayed #16
Comments
Correct, https://html.spec.whatwg.org/multipage/media.html#attr-media-controls In addition to |
Thanks I was not aware of that attribute. There will be a map-specific list of controls that we will need to define and specify. |
The That said, the way it is currently defined (as a block list of |
Help me understand why that is too narrow. |
The problem comes when you want to have both default and custom controls as part of the map widget layout (as discussed in #79 ). HTML video doesn't currently have this option: you can create buttons on your web page that affect the video, but you can't add buttons to the video control panel itself. To match how the libraries currently do it, you'd need to be able to specify which default controls get shown in which corners of the map. |
This issue is for discussion of the map viewer capability "Toggle whether default controls are displayed".
Using the
<video>
element as an example, the browser renderer is capable of rendering video content on demand of the author using something as simple asThe video player rendered by that has default controls, styled according to the particular browser implementation. Yet, and I am not an expert, but I believe you can shut the controls off (by omitting the
controls
attribute) and provide your own controls (if you wish) which respond to events (handled by script).Maps should follow a similar approach: if you don't want default controls, don't ask for them. Then, use events emitted by the map 'player' to bind your own self-created controls to the map, with script.
The text was updated successfully, but these errors were encountered: