logo

blog

My website can't be that messy, right? git clone https://hacktivis.me/git/blog.git
commit: 106f729b37e8516240f3130a40eec349601e01cf
parent 7d213a8c180d27ca1024a792f9ce323ebbc444a3
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date:   Tue, 17 Aug 2021 13:49:33 +0200

notes/pure-wayland: Improve firefox/chromium descriptions

Diffstat:

Mnotes/pure-wayland.shtml4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/notes/pure-wayland.shtml b/notes/pure-wayland.shtml @@ -123,8 +123,8 @@ endif</code></pre> <li><a href="/projects/badwolf">Badwolf</a>: Yes, Fully tested and supported as first-class citizen</li> <li><a href="https://wiki.gnome.org/Apps/Web">epiphany - Gnome Web</a>: Yes, seems to work fine, should be well supported</li> <li><a href="https://www.netsurf-browser.org/">netsurf</a>: GTK3 frontend just works</li> - <li><a href="https://www.mozilla.com/firefox">Mozilla Firefox</a>: No, requires X11 libs and Wayland support is quite bugged, screen grabbing doesn't works without xdg-desktop-portal (dbus-based) and the indicator has it's own top-level window</li> - <li><a href="https://chromium.org/">chromium</a>: Not really, requires to enable ozone, which probably means compiling it yourself (You had one job binary-based distros)</li> + <li><a href="https://chromium.org/">chromium</a>: Not really, requires to enable ozone, which means compiling it, something I'd rather not do</li> + <li><a href="https://www.mozilla.com/firefox">Mozilla Firefox</a>: No, segfaults when compiled without X11 libs. Wayland support is a horrible mess (ie. microphone/camera grab is a top-level window); screen-grabbing uses GNOME's xdg-desktop-portal, which is dbus-based instead of wayland-based <code>wlr_screencopy</code>.</li> </ul> <h2 id="games">Games <a class="hlink" href="#buildsystems">ยง</a></h2>