📝 Add Xwayland hyprland note

Author: Schneegans

src/content/docs/installation-on-linux.mdx

@@ -178,8 +178,13 @@ It is perfectly fine to use the same shortcut ID for multiple menus.
 Use this in combination with the app-dependent menu feature to open different menus depending on the currently focused application!
 
 ### <Icon name="simple-icons:hyprland" class="inline-icon" /> Hyprland
+
 ![hyprland image](../../assets/img/hyprland-shortcuts.png)
 
+Kando works quite well on Hyprland, but you will need to do some additional setup.
+
+#### Window Rules
+
 You will need some window rules for Kando.
 Else, the menu will not float above other windows.
 
@@ -194,6 +199,8 @@ windowrule = float, class:kando
 windowrule = pin, class:kando
 ```
 
+#### Shortcuts
+
 Also, Kando cannot directly bind global shortcuts on Hyprland.
 Instead, you specify a shortcut ID for each menu in Kando's menu editor and bind a key combination in `hyprland.conf`.
 To get the exact shortcut ID, you can use `hyprctl globalshortcuts` to list all currently registered global shortcuts.
@@ -204,19 +211,34 @@ If you run the flatpak version of Kando and chose `example-menu` as the shortcut
 bind = CTRL, Space, global, menu.kando.Kando:example-menu
 ```
 
-#### Furthermore
-1. Toggling Special-Workspace through kando-menu will be glitchy (i.e in some cases special-workspace will reopen instead of closing). See https://github.com/kando-menu/kando/issues/784
-2. After triggering kando-menu-item of type `Run command` whose target is `activewindow` will not work correctly as by default Hyprland restores focus_on_close to next candidate window. See https://github.com/kando-menu/kando/issues/812
+#### Use Wayland instead of XWayland
+
+Per default, Electron apps like Kando run under XWayland.
+On Hyprland, this can lead to some glitchy behavior like menus opening not at the cursor or dropdown menus not working correctly.
+You can fix this by making your Electron apps run under Wayland instead of XWayland.
+To do this, add the following line to your config:
+
+```
+// ~/.config/hypr/hyprland.conf
+env=ELECTRON_OZONE_PLATFORM_HINT,auto
+```
+
+#### Input Issues
+
+Toggling Special-Workspace through kando-menu will be glitchy (i.e in some cases special-workspace will reopen instead of closing). See https://github.com/kando-menu/kando/issues/784.
+
+After triggering kando-menu-item of type `Run command` whose target is `activewindow` will not work correctly as by default Hyprland restores focus_on_close to next candidate window. See https://github.com/kando-menu/kando/issues/812.
+
+Both of above can be solved by using the following config:
+```
+// ~/.config/hypr/hyprland.conf
+input {
+    special_fallthrough = true # having only floating windows in the special workspace will not block focusing windows in the regular workspace.
+    focus_on_close = 1 # focus will shift to the window under the cursor.
+}
+```
 
-   Both of above can be solved by using the following config
-   ```
-   // ~/.config/hypr/hyprland.conf
-   input {
-       special_fallthrough = true # having only floating windows in the special workspace will not block focusing windows in the regular workspace.
-       focus_on_close = 1 # focus will shift to the window under the cursor.
-   }
-   ```
-3. Using the solution for 2nd step might not work in situations where the target window is small as you will travel out of target area while activating items from sub-menu. For that you can use `hyprctl dispatcher focusurgentorlast` or `hyprctl dispatcher focuscurrentorlast` instead. See https://wiki.hyprland.org/Configuring/Dispatchers/#list-of-dispatchers
+Using the solution for 2nd step might not work in situations where the target window is small as you will travel out of target area while activating items from sub-menu. For that you can use `hyprctl dispatcher focusurgentorlast` or `hyprctl dispatcher focuscurrentorlast` instead. See https://wiki.hyprland.org/Configuring/Dispatchers/#list-of-dispatchers.
 
 ### <Icon name="simple-icons:wayland" class="inline-icon" /> Niri
 
@@ -233,10 +255,9 @@ window-rule {
 }
 ```
 
-#### Furthermore
-1. Using hotkey press simulation through Kando will not work for triggering keybinds registered in your Niri configuration. In that case, have Kando run a command ```niri msg action <action>``` where the action is the one configured in the your configuration along with its arguments (for example `niri msg action focus-workspace-up` or `niri msg action focus-workspace 1`)
+Using hotkey press simulation through Kando will not work for triggering keybinds registered in your Niri configuration. In that case, have Kando run a command ```niri msg action <action>``` where the action is the one configured in the your configuration along with its arguments (for example `niri msg action focus-workspace-up` or `niri msg action focus-workspace 1`)
 
-2. Niri does not yet support global shortcuts. But you can open menus using 'kando --menu \"Menu Name\"' from the command line or from your niri config.
+Niri does not yet support global shortcuts. But you can open menus using 'kando --menu \"Menu Name\"' from the command line or from your niri config.
 
 ### Dusk