Thanks for review & testing!

BTW, a few things things to note:

libsoup3 is fairly recent (2021-09-18), and e.g. not available in Debian before Bookworm (12, current stable)
I probably won't make it possible to support both libsoup2 and libsoup3, because the changes are too complex which would make the code somewhat of a nightmare.
This means that other plugins have to be compiled against e.g. webkit2gtk 4.1, not 4.0.

Is that OK with everybody? @elextr @frlan It is with me, I feel it's OK for the plugin to live in the present, and with the webkit question we don't really have a choice (apart from process isolation). Also, maybe this means we want to drop support for webkit2gtk 4.0 in the other plugins, or have a fancy check in the build system to try and avoid the case where different plugins use incompatible libraries -- but that's gonna be non-trivial, and probably not worth it.

Also a subsequent improvement would be to use the asynchronous libsoup API, because now it blocks the UI. Before this PR, it looked a bit better because IIUC (not verified) one of the libsoup calls spun the main loop manually, but this likely had some unexpected side effects of its own. I will try not to include this here.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.