tinywrkb

While the changes were merged, there is no updated build in the Flathub repo yet, as the chromium-qtwebengine commit was outdated. I'll run the tests when we have a new...

We have now the sanboxing support, but there seems to be a regression with the tests, something about not having dbus daemon running. ``` Failed to connect to the bus:...

After looking at this today, I found the problem. Not surprising, I introduced the issue myself by adding the Flatpak sandboxing support. As far as I can tell, there's no...

@The-Compiler this seems safe to close, I don't see a problem with a recent pdf.js version. BTW, there's now an interesting [`forcePageColors` setting](https://github.com/mozilla/pdf.js/blob/b0a3c9e8cf84e3d20e754c6c2ab6650f3928d62d/extensions/chromium/preferences_schema.json#L216).

I tried today QtWebEngine `v6.4.0-beta1` with Chromium `98.0.4758.90` built against the KDE 6.3 Flatpak runtime (Qt 6.3.x) and WebRTC screen sharing with PipeWire seems to be broken. The log does...

The beta channel of the Flathub app is now (finally) updated to QtWebEngine `6.3.1` with Chromium `94.0.4606.126+`.

Flatpak test builds with development releases of QtWebEngine `6.4` (Chromium `98.0.4758.90`) are available [here](https://github.com/flathub/org.qutebrowser.qutebrowser/pull/226). I believe that this is the first time building QtWebEngine with the app, and not pulling...

[Seems to be hardcoded](https://invent.kde.org/qt/qt/qtwebengine/-/blob/e2c04460bfc5dcc70886770e0c53faab89b4b43e/src/core/web_engine_context.cpp#L921), so it will be wrong for the Flatpak app, as we build the latest commit in the relevant qtwebengine-chromium branch. Qt's devs are just too slow...

@krisko this is a great suggestion! It actually makes the UI more responsive. I'm getting better performance here with sixel previews. This might be worthy to be added as a...

Note that Flatpak requires apps to ship their own icons, so using one from the icon theme will block a possible Flathub submission.