qutebrowser VS qtwebkit

I don'r know if this counts but there is also https://www.qutebrowser.org/ which uses qt webkit IIUC

I searched this issue and saw there were already open issues on github, and it is an upstream issue with QtWebEngine.

You can add [aria-haspopup] to your hints.selectors setting (from a config.py, see the configuration docs) to get the same effect.

There is a small how-to here: Switching to Qt 6 by default · Issue #7202 · qutebrowser/qutebrowser

There is a Qutebrowser user script for 1password: https://github.com/qutebrowser/qutebrowser/blob/master/misc/userscripts/qute-1pass. Disclaimer: I am the original author (it’s been refactored a lot by mkonig since I originally wrote it). My original version is here https://github.com/tomoakley/dotfiles/blob/master/qutebrowser/userscripts/1password

Glad to hear! You'd either add it to the userscripts folder in the repo, or add a link to the README about it and host it elsewhere.

It seems to work fine with Qt 6, so I guess this is just some missing feature on Qt 5. Maybe something changed on Wikipedia's side.

Show PID in :process error message · qutebrowser/qutebrowser@c41f152

Not so ancient - Otter uses QtWebKit 5.212 from Mar 10, 2020.

AFAIK, Otter Browser uses the latest QtWebkit-ng on Windows. It scores 341 points in HTML5Test. There is also an experimental Qt WebEngine backend.

The main backend for Otter Browser is QtWebkit Reloaded, last updated in 2020, see the screenshot.

As for Otter Browser, there is a bug in QtWebKit. Try using Otter Browser on Qt WebEngine.

Otter Browser is based on QtWebKit-NG, which is from 2020, so still relevant. That said, you can use the nightly WebKit build from Playwright: https://i.postimg.cc/Fz7FwRQW/Playwright.png

Lastly, the other webkit based project, QtWebkit. It is also very lightweight and fast, It also provides a cross-platform render and It has access to the system dialogs. The down side is that you will have to make a Qt App to use it. If you don't want to implement it, then you cannot use It

> I hate that it's based on Chromium though

There aren't really many alternatives. The main one is WebKitGTK, but that comes with its own set of issues (mostly performance/compatibility). You can use qutebrowser with QtWebKit as well, but I wouldn't recommend it - it's based on a 2018 WebKit with many known security issues: https://github.com/qtwebkit/qtwebkit/releases

I had hoped for Servo to fill that gap at some point, but so far that hasn't happened yet: https://github.com/servo/servo/issues/27579

Another possibility is for Geckoview to be ported to Desktop platforms some day: https://mozilla.github.io/geckoview/ - something the people behind Tridactyl would like to happen: https://tridactyl.xyz/ideas/#port-geckoview-to-x86_64

> and Qutebrowser privacy related settings also seem quite limited compared to Firefox... (and even compared to Chromium.)

Can you be more specific? Pretty much anything that's possible to expose (either via a QtWebEngine API or via Chromium commandline arguments) is exposed. Certain things (like deleting cookies belonging to a tab when it's closed) just aren't possible without implementing them in QtWebEngine first unfortunately.

FWIW there's an overview here: https://github.com/qutebrowser/qutebrowser/issues/4045

and Qt has mostly moved to qtwebengine/blink. qt-webkit is sort-of-not-really maintained by very few volunteers. https://github.com/qtwebkit/qtwebkit/releases

While you can still use it with QtWebKit instead, I wouldn't recommend doing so, as that's still based on a 2018 WebKit with no process isolation or sandboxing.