Stop a new Chrome tab ignoring scroll and the spacebar until you refocus
Re-checked the earlier correction on 4.0.4-1 and it holds: /usr/share/omarchy/default/hypr/windows.lua lines 9 to 19 carry the class = "^$", title = "^$", xwayland = true, float = true, fullscreen = false, pin = false no_focus rule, and /usr/share/omarchy/config/chromium-flags.conf passes --ozone-platform=wayland. omacom/omarchy#11419 is still open and its workaround is hyprlang. The hyprland-wiki window-rules source (content/configuring/core/rules/window-rules.md) documents hl.window_rule({ match = {...} }) with match fields class, title, float, fullscreen, pin and xwayland and the no_focus effect, so the Lua rule is valid. ~/.config/hypr/hyprland.lua exists on Omarchy 4 and says to add personal configuration at the bottom. Arch ships hyprland 0.56.2. The only defect is a source: https://wiki.hypr.land/Configuring/Window-Rules/ returns 404, while https://wiki.hypr.land/Configuring/Basics/Window-Rules/ returns 200 and is the URL Omarchy's own windows.lua cites. Fields left unchanged to preserve the earlier corrected status. Not exercised: I did not add the rule or reload Hyprland on this workstation.
The rule stops every floating native Wayland window with an empty class and title from taking focus. If some other app relies on such a window for input, it will need a click to focus. Remove the rule if that happens.
Symptom
Right after I open a new tab in Chrome or Chromium (running natively on Wayland), mouse wheel scrolling and the spacebar do nothing in the page. Clicking another window and back into Chrome fixes it instantly. Happens on Omarchy with the default Wayland flags.
Cause
Chrome briefly creates a transient floating toplevel with an empty class and empty title. Hyprland gives a new window focus, so that invisible surface takes keyboard and pointer focus and the visible tab gets no input until focus is forced back. Omarchy already has a no_focus rule for exactly that signature in /usr/share/omarchy/default/hypr/windows.lua, but it is scoped to xwayland = true. Chromium on Omarchy runs natively on Wayland because Omarchy's chromium-flags.conf passes --ozone-platform=wayland, and Google Chrome does too when it is started with that flag or picks Wayland itself, so the rule never matches. Reported as omacom/omarchy#11419, open. The reporter's workaround was written in hyprlang syntax, which Omarchy 4's Lua config does not read.
Fix
Add an equivalent rule for native Wayland windows at the bottom of ~/.config/hypr/hyprland.lua (Hyprland 0.55+, which is what Omarchy 4 and current Arch ship):
hl.window_rule({
match = { class = "^$", title = "^$", float = true, fullscreen = false, pin = false, xwayland = false },
no_focus = true,
})
Then reload from a keybind or run hyprctl reload yourself, and restart the browser.
To see the surface yourself, run hyprctl clients right after opening a tab and look for a floating client with class: and title: both empty and xwayland: 0.
Verify
Open a new tab with Ctrl+T, load a long page and scroll immediately with the wheel and the spacebar without clicking. It scrolls.