I’m having issues with Anki lacking support for some CSS features due to the use of Chromium 112. The latest version of Qt (6.8.1) supports Chromium 127.
Some Anki packages (such as the AUR) appear to have no problems providing Qt 6.8. Qt 6.6 which Anki provides for Windows is out of the standard support window for Qt.
Would it be rational/possible for Anki to use the system webview rather than bundling its own webview?
This will ensure that the user can always use the latest version of webview, irrespective of the Anki version or the Qt version. In addition, it will also reduce the size of the app.
not sure if there’s any pre-existing & maintained library for that?
one move is to write it as a PWA, use service workers for offline reviews and such. would work for mobile devices too, so you no longer need ankidroid&ankimobile, everything is in one codebase. feels like thats a larger project to take on though.
Replacing more of the code with web components is definitely a larger project. But, I wasn’t talking about that.
Currently, Anki is using Qt’s bundled webview to render things like the cards in the reviewer, the stats page, the card info page, etc. Can Anki instead use the system’s webview (e.g. Microsoft Edge WebView2 on Windows) to render the same pages?
As it stands, having an embeddable webview is important for the deck overview page (3 webviews in a trenchcoatQVBoxLayout) and the editor (when embedded in the browser) etc.
Today I stumbled on the same issue; Chromium 120+ is required for CSS Nesting.
I tried Release 25.01beta1 · ankitects/anki which includes the aforementioned commit to upgrade Qt to v6.8.1. It seems that Chromium shipped with this version is 122.