Open saif-o99 opened 8 months ago
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 <audio>
and <video>
. For example, it might make sense to have the capability, but not to support "controls" on native (which renders default controls on web).
IMO, the subset that makes sense to me for <video>
is:
<source>
children to set possible sources along with MIME types for formatsfor my case a chat application that has messages, audio recordings, audio files, video files. and many more types of messages.
so when i was using <audio>
on the website. now on the mobile i've to install a package to play sound, like react-native-sound
.
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. Thanks
Describe the feature request
Support the video element & audio element. These elements are not currently supported on native.