Ricardo Wurmus <rek...@elephly.net> writes: > Hi Mike, > > thank you for your patient reply. > >> Ricardo Wurmus <rek...@elephly.net> writes: >> >>> Does the code include DRM support, for example? Does it phone home? >>> Can we see the patches that upstream applied to the Chromium sources? >>> >> >> QtWebengine does not handle DRM at all. That is handled by a 3rd party >> plugin called wildevine and would require guix to bundle that plugin. >> Something I'm confident is not going to happen. As an added measure my >> proposed qtwebengine declaration has pepper plugins disabled making it >> impossible to load 3rd party plugins either way. >> >> see https://doc.qt.io/qt-5/qtwebengine-features.html#html5-drm >> for reference > > I’m aware of this. My apologies for not expressing myself more > clearly. We probably want to remove the support for the DRM plugin, > following the discussions about ungoogled-chromium at > > https://issues.guix.gnu.org/issue/34565
Marius Bakke does a good job of summing up DRM when closing this issue. Widevine and DRM are not part of chromium and requires not only the widevine binary to be installed by the user. But also in the case of qtwebengine requires the users to rebuild the package to include pepper plugin support. The proposed declaration uses this flag -webengine-pepper-plugins=no which disables flash and widevine support altogether. see https://code.qt.io/cgit/qt/qtwebengine.git/tree/config_help.txt?h=5.12.6#n16 for reference. Mike