-
Notifications
You must be signed in to change notification settings - Fork 167
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
(feature) <video> <audio> elements #41
Comments
This would need more details on the use case. Typically apps will use media players that are self-contained, complex UI components (e.g. YouTube player) on every platform. It's unlikely we'd prioritize this above APIs already identified in the compatibility table, but more details would be useful. For example, I know Expo has xplat modules for media players, and the faster path forward might be for those components to get a web-compatible API so this project can take them on as a dependency. |
I think it's useful to decide the subset of the API that we might want for IMO, the subset that makes sense to me for
|
for my case a chat application that has messages, audio recordings, audio files, video files. and many more types of messages. I understand these two tags won't be easy to implement. but anyway i added an issue here to know your opinon for the possability. |
Describe the feature request
Support the video element & audio element. These elements are not currently supported on native.
The text was updated successfully, but these errors were encountered: