Jan Lukas Gernert

I have a super hacky branch for Gtk4 here: https://github.com/jangernert/webkit2gtk-rs/tree/gtk4 Just enough for me to port my application to Gtk4. For this to work you still need to compile webkitgtk...

I don't see any reason for that. It's just as easy to reference the fork in your cargo.toml. And once webkitgtk 5.0 is released and packaged I would start generating...

You should try the official WIP bindings: https://gitlab.gnome.org/World/Rust/webkit2gtk5-rs You'll need to use the Gtk-Bindings from git as well.

@jeena there is no `webkit2gtk` anymore. The new API is called `webkitgtk-6.0` and there are rust bindings here: https://gitlab.gnome.org/World/Rust/webkit6-rs

I hit this one as well. It think it is caused by libxml2 changing the default encoding when `NULL` is passed from `utf-8` to `ISO-8859-1` which apparently is more correct....

@dginev I created a branch that fixes the problem for me: https://github.com/jangernert/rust-libxml/commit/5c9591d40b4672d03dd4d832d9443f130448ac83 There are only 2 questions: - does this possibly mess up something else? - should this also be...

A runtime error would be sufficient I guess. If with some rust magic that error could be moved to compile time I would be even happier. With the behaviour as...

> I found a workaround for this which seemed to solve the issue for me: Managed to log in with this. But I didn't set the client id/secret.

Thanks! Works fine from what I can tell on first glance. I personally didn't expect the player to be a separate window rather than a dialog or a navigation view...