libinput-gestures VS org.chromium.Chromium

With chromium-based like chrome or chromium, this is not the case but at least I can use libinput gesture to allow navigation using 3 fingers (4 are for workspaces and apps switching). Now, I've enabled wayland on these browsers (set ozone-platform=wayland) and there are these issues:

I don't think there are native gestures in qtile. I use fusuma, since it works better for me on X11 and wayland, but I've also used libinput-gestures in the past when on X11, and that works too.

I personally use libinput-gestures to call commands using touchpad gestures. You can also combine it with ydotool to bind macros and such to your gestures, e.g. 4 fingers swipe down closes the current window, 3 fingers swipe left or right changes workspace, etc

$ sudo apt-get install libinput-tools $ git clone https://github.com/bulletmark/libinput-gestures.git $ cd libinput-gestures $ sudo ./libinput-gestures-setup install $ libinput-gestures-setup autostart start

if using wayland, try https://github.com/OneAdder/libinput_gestures_qt and https://github.com/bulletmark/libinput-gestures

The github has quite a lot of info, so hopefully we can find the right config for what we need on there https://github.com/bulletmark/libinput-gestures

You can easily configure a custom key shortcut to open the "Quick Note" window with a keyboard shortcut. If you really want to run this with a drag-from-edge gesture, I think you can configure a drag gesture with LibInput-Gestures, but I have never tried this for myself.

Seems like it's a buggy wayland fractional scalling implementation... It's reverted in the chromium flatpak https://github.com/flathub/org.chromium.Chromium/commit/eea7af903decb3a3b9bb6fdacbb55d24a90e18f3

My philosophy has been to let the distro package manager handle system packages (kernel, OpenSSL, etc) but then use flatpak [1] to install user progs like Chromium and VSCode so I get bleeding edge releases and sandboxing.

[1] https://flathub.org/apps/details/org.chromium.Chromium

If it helps I'm using https://flathub.org/apps/details/org.chromium.Chromium along with https://flathub.org/apps/details/com.github.tchx84.Flatseal

You can inspect how Chromium is built on Flatpak here: https://github.com/flathub/org.chromium.Chromium

Oh that doesn't work? Hmm I wonder if you could try the executable listed at https://flathub.org/apps/details/org.chromium.Chromium and put that in your config?

No need to trust anything, unlike snaps, the way they're distributed is public and open source: https://github.com/flathub/org.chromium.Chromium

Would a workaround be installing chromium from flathub, and using that for browsing? https://flathub.org/apps/details/org.chromium.Chromium