[Sailfish 3 Updates] WebEngine and Encrypted Media Extensions?

asked 2018-03-15 17:23:56 +0300

jgueytat gravatar image

updated 2018-03-23 14:54:55 +0300

The version of QtWebEngine since Qt 5.7 does handle the Encrypted Media Extensions functionality which leads to native Netflix or Spotify applications.

You can have a look at the Spotify Web Playback SDK.

So the question:

Will we with the WebEngine from Sailfish 3 in our application be able to enable Encrypted Media Extensions ?

Page to check the Encrypted Media Extensions in your current browser : https://bitmovin.com/mpeg-dash-hls-drm-test-player/ .

I have on Github an example of what I would like to run on Sailfish OS.

edit retag flag offensive close delete



A backport from the two modules QtNetworkAuth and QtWebEngine might be possible. At least QtNetworkAuth is not a problem. https://github.com/jgueytat/UnofficialSpotify

jgueytat ( 2018-03-15 17:29:09 +0300 )edit

I hope this will come one day. A native Spotify app would be awesome. I'm looking forward to write an app myself.

scharelc ( 2018-03-17 01:53:01 +0300 )edit

Implementing DRM into the system does not really match my expectations to SFOS and its open, free roots. However, I see no issues in implementing it in a stand-alone app.

ghling ( 2018-03-17 14:57:05 +0300 )edit

It's not really implementing DRM. It's enabling a functionality which is already enabled in the current Sailfish OS browser by the way. Check this website : https://bitmovin.com/mpeg-dash-hls-drm-test-player/ . The point is to enable it also in a WebEngineView.

So the question remains for the promised WebEngine. As we need time to create the applications the soonest we have the answer the best!

jgueytat ( 2018-03-20 11:18:31 +0300 )edit

Nevertheless, EME is nothing else than DRM, included in the HTML5 standard (and thus needs to be implemented on browser / web engine level). I don't want to spark the whole EME discussion again. Adding it to the stock browser (which is included in the system) by default does not represent my perception of the principles of SFOS. As I said, there is nothing wrong with offering it as additional feature (like installing an optional package, a stand-alone app etc) or maybe add an option for the user to enable it if desired (like many other browsers are doing it). But the default setting IMO should be disabled.

ghling ( 2018-03-20 11:59:35 +0300 )edit