Hi, if your application depends on both GTK 4 and WebKitGTK, this announcement is important for you.
I failed in my goal to prepare a stable GTK 4 API for WebKitGTK in time for GNOME 43 and WebKitGTK 2.38. I am finally on track to stabilize the API for GNOME 44 and WebKitGTK 2.40. There will be several changes:
- The pkg-config API version will change from
webkitgtk-5.0as I’ve removed more vestiges of the legacy WebKit2 branding
- There will be many small API changes, which you can follow in 210100 – (GTK4) [META][GTK][GTK4] Support GTK4
This will be moderately disruptive when WebKitGTK 2.40 is released in March next year alongside GNOME 44. The problem is distros will release WebKitGTK 2.40 to stable users, but it will contain a different GTK 4 API and ABI than WebKitGTK 2.38. Applications that use GTK 4 will all need to be patched to use the new API version and then recompiled. This will be annoying for stable distros, but my expectation is it should be manageable because there are only a few such applications. In GNOME core, that is only gnome-builder and gnome-initial-setup. These should both be quite easy to handle. Distros will need to bundle all these updates together so that everything that depends on WebKitGTK for GTK 4 will be updated in tandem with WebKitGTK 2.38 → 2.40 to avoid breaking users.