Comments (4)
I like the idea! The native <video>
element has built-in speed controls, but it does not expose an API to control or define the increments. I think it would be a nice idea to explore making that a first-class feature. WICG is the right place to initiate the discussion and gauge interest: https://discourse.wicg.io/
from media-ui-extensions.
I can discuss in that forum but I understood from the readme this repo was the brainstorm hub to be later discussed over there?
proposals to be something that we can eventually propose to the Media WG or WhatWG
@heff Do you want me to hone the idea here first, or the WICG discourse?
from media-ui-extensions.
@tomByrer per @igrigorik's callout, that request feels better suited for WICG, since it requires an actual UI change as well, though happy to discuss here as well. We've tended to keep media-ui-extension proposals focused on exposing data/information in a predictable and well defined way that can then be used by custom UIs.
You may be interested in Media Chrome (for this case, our <media-playback-rate-button>
), which is where we've been trying to build "player agnostic UI components/architectures". We've actually just added support for 3 of the media-ui-extension proposals to Media Chrome:
- Stream Type (needs to be converted to an official proposal per our new process)
- DVR State (needs to be converted to an official proposal per our new process)
- Live Edge Window (our first official proposal using our new process)
Feel free to reach out with any followup discussions, and it's definitely fine to continue the conversation around this particular proposal.
from media-ui-extensions.
@cjpillsbury and I talked about this IRL and from that, revising what he said before a little, we're happy to have the conversation happen here if it can result in a refined proposal or more concentrated engagement. We do generally focus on the media element APIs that could unlock custom UI features, rather than browser-built-in UIs which are inherently all different to begin with. But there's also enough overlap that it's at least loosely relevant. So discuss away! At the same time I'd encourage everyone to post on wicg in parallel, to not delay awareness and gather interest on that side.
from media-ui-extensions.
Related Issues (9)
- Playback quality selection HOT 14
- Invoker HTML buttons HOT 2
- Warning API
- Ads
- Stream Type - Proposal HOT 27
- DVR State - Proposal HOT 14
- Live Edge Window HOT 12
- Process Follow-ups
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from media-ui-extensions.