WebOS native HLS support vs. third-party libraries

Web App Development
1

WebOS has some documentation on which HLS tags it supports.

However, there is something I don’t understand. If I use third-party web-based library for HLS, such as hls.js or shaka, aren’t those specifications irrelevant? After all, the third-party library is a separate, independent implementation of the HLS protocol: these libraries have their own specifications of which HLS tags they support.

I would think that the WebOS documentation refers to it’s own implementation of the HLS protocol. If I understand correctly, it has it’s own implementation of one.

But, e.g., in their sample app, MediaPlayback, although shaka is used there for playback, they send the user to their documentation on HLS support.

My question is: if I use a third-party library, such as hls.js, shouldn’t I rely on their documentation for which tags and which browsers they support instead of the WebOS specification?

2

As you mentioned, the webOS platform has a native HLS player, and the webOS specification is for it. If you use a third-party player, only the decoding and rendering functionality of the webOS platform will be used. Therefore, you should refer to the documentation of your third-party player, such as hls.js, for the HLS tags it supports. Thank you.