Yes sorry! Rendering of the app is attempted with the system's webviewer, which in the case of Linux the program tries to use webkit (as noted). I'll try to do some testing on one of these distros where it is not bundled coming up, but I'm not sure I can promise a good fix for this as it's central to the construction.
The drawback is needing that dependency installed, but the benefit is that it's only installed once: binaries never need to include it, and if other programs attempt to use the system webviewer they will also rely on the same instance.
Perhaps I should list the dependency requirement somewhere so that it is more explicit.. What do you all think?
It’s definitely better to use the system web view. Including all of WebKit in the static binary is clearly not a good option. I think the easiest solution would be to document the dependency, and to have a better error message than just getting the “No such file or directory” from the linker.
I’d mention that WebKit2GTK is very much specific to GTK. The equivalent used on QT based desktops like KDE is QtWebEngine (or QtWebKit? (it’s a bit confusing)).