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 In regards to QtWebEngine phoning home https://wiki.qt.io/QtWebEngine states all google services have been removed. Nothing I've seen indicates this is not the case. In terms of patches. You can get a complete diff of chromium sources by cloning qtwebengine recursively like so. --8<---------------cut here---------------start------------->8--- git clone http://code.qt.io/qt/qtwebengine.git --recursive --8<---------------cut here---------------end--------------->8--- Version 5.12.6 of qtwebengine is based on chromium sources 69.0.3497.128 to get a complete diff you can do this from the src/3rdpath directory. you can then get a complete patch diff for version 5.12.6 like so. --8<---------------cut here---------------start------------->8--- git diff origin/upstream-master origin/69-based --8<---------------cut here---------------end--------------->8--- see https://wiki.qt.io/QtWebEngine/Rebase_on_New_Chromium for reference Mike
