[GH-ISSUE #223] [Launcher] Ability to focus fullscreen apps on Hyprland #4318

Open
opened 2026-05-23 00:52:38 +01:00 by JakeStanger · 2 comments
Owner

Originally created by @donovanglover on GitHub (Jul 4, 2023).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/223

Describe the bug
When a workspace has a fullscreen window, clicking on another application on the same workspace will switch to it and have focus, but won't be visible to the user.

Similarly, floating windows are hidden behind other windows that are also floating.

To Reproduce

  1. Open 2 applications
  2. Make one fullscreen
  3. Change workspaces
  4. Click the icon of the application that isn't fullscreen

Expected behavior
User should see the application they clicked. Fullscreen can be disabled and bringactivetotop can be used for floating windows

System information:

Additional context

Originally created by @donovanglover on GitHub (Jul 4, 2023). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/223 **Describe the bug** When a workspace has a fullscreen window, clicking on another application on the same workspace will switch to it and have focus, but won't be visible to the user. Similarly, floating windows are hidden behind other windows that are also floating. **To Reproduce** 1. Open 2 applications 2. Make one fullscreen 3. Change workspaces 4. Click the icon of the application that isn't fullscreen **Expected behavior** User should see the application they clicked. Fullscreen can be disabled and `bringactivetotop` can be used for floating windows **System information:** - Distro: NixOS - Compositor: Hyprland - Ironbar version: https://github.com/JakeStanger/ironbar/commit/f8d8c063008340922b20aa665d8f893ab63e82d7 **Additional context** - https://github.com/hyprwm/Hyprland/issues/1234
Author
Owner

@JakeStanger commented on GitHub (Jul 5, 2023):

I think this is related to #183. It seems to be one or more bugs (or at least unexpected behaviours) (confirmed working as expected by Vaxry) with how Hyprland handles giving window focus.

The launcher calls activate on the underlying toplevel through Wayland directly, which means it's up to the compositor to actually handle the request.

A possible workaround might be to add some kind of config option, so you can run a script when the button is clicked instead of calling wayland. I may also be able to hook into the Hyprland IPC. Ideally though, I'd rather see it fixed upstream.

<!-- gh-comment-id:1621604637 --> @JakeStanger commented on GitHub (Jul 5, 2023): I think this is related to #183. It seems to be one or more ~~bugs (or at least unexpected behaviours)~~ (confirmed working as expected by Vaxry) with how Hyprland handles giving window focus. The launcher calls `activate` on the underlying toplevel through Wayland directly, which means it's up to the compositor to actually handle the request. A possible workaround might be to add some kind of config option, so you can run a script when the button is clicked instead of calling wayland. I may also be able to hook into the Hyprland IPC. Ideally though, I'd rather see it fixed upstream.
Author
Owner

@donovanglover commented on GitHub (Jul 6, 2023):

Custom scripts could be nice since users would be able to use swapwithmaster and other dispatchers. I'd like to automatically make windows master when clicking on them.

<!-- gh-comment-id:1624190932 --> @donovanglover commented on GitHub (Jul 6, 2023): Custom scripts could be nice since users would be able to use `swapwithmaster` and other dispatchers. I'd like to automatically make windows master when clicking on them.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
JakeStanger/ironbar#4318
No description provided.