Preliminary Wayland support
Bug #975355 reported by
Darxus
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Midori Web Browser |
Fix Released
|
Low
|
Unassigned |
Bug Description
To work with wayland, gdk_x11_ calls and Xlib calls need to be wrapped in build-time and run-time backend checks: http://
$ grep -r gdk_x11 .
./midori/sokoke.c: Atom save_mode_atom = gdk_x11_
./midori/
$ grep -r Xlib .
./midori/main.c: #include <X11/Xlib.h>
http://
The wayland backend in GTK+ 3.4 works, so as soon as these are done midori should be usable with wayland.
tags: | added: wayland |
summary: |
- Wayland support + Preliminary Wayland support |
Changed in midori: | |
status: | In Progress → Fix Released |
importance: | Undecided → Low |
To post a comment you must log in.
I put some work into getting webkitgtk working with wayland and then tested out midori. We do indeed need runtime checks in a few places. The attached patch is a good start, but we need to do some other work to make Wayland (and other GDK backends) work perfectly with midori, e.g. add runtime checks for the version string instead of always "X11" if it was available at compile time.
To get webkitgtk 1.8.3 to build, I had to reimplement webkit's GtkWidgetBackin gStoreX11. cpp in terms of wayland surfaces, and to do /that/ I had to make the symbol gdk_wayland_ create_ cairo_surface (in GTK3) visible; presumably those two packages will make their own efforts to fix things, but in the meantime this was enough to get midori up and running. It should be noted that libunique3 is not wayland-compatible; I had to pass --disable-unique to configure.
I'll submit additional bug reports for fixes to individual wayland-specific issues, but this is, again, enough to build and run for now.