mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[FEAT]: Extend windows' clickable edges across Komorebi's borders for easier interactions #406
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @igorcmoura on GitHub (Jun 12, 2024).
Is your feature request related to a problem? Please describe.
When running Komorebi without padding, and even without borders, the elements at the edges of the windows are not clickable anymore from the far edge of the screen.
For example, without Komorebi running, when Chrome is on fullscreen I can move the mouse to the far top of the screen and click on a tab, or move the mouse to the far right and interact with the scrollbar. This is way easier than precisely aiming the mouse at a tab or scrollbar to click it. However, applications lose this functionality when Komorebi is running.
Note that even without Komorebi running this effect doesn't work if the application is not on fullscreen.
Describe the solution you'd like
It would be nice if Komorebi extended the applications' clickable edges across its borders. So when a border is clicked, the effect is that the click is redirected to the application at the closest point from the mouse position.
Describe alternatives you've considered
I'll probably work around it with an AutoHotkey script.
Additional context
Without Komorebi running:
https://github.com/LGUG2Z/komorebi/assets/8890509/6d5297d1-87f2-4a1a-84aa-060a008d1fab
With Komorebi running and with borders:
https://github.com/LGUG2Z/komorebi/assets/8890509/2cece0f5-3140-42aa-adee-0dbc0003a33c
With Komorebi running and no borders (some edges seem to still work):
https://github.com/LGUG2Z/komorebi/assets/8890509/2dfdc073-43d5-4fae-a7df-3303fba93135
I'm not an UX designer, I just found some articles about it, but in UX design there is this guideline that comes from Fitts' Law that's usually called "Rule of the infinite edges" or something similar. It says that placing targets at the far end of the screen greatly reduces the time the user takes to interact with the target, since they can move the mouse at maximum speed towards it and still hit it.
Sources:
https://www.uxtoast.com/ux-laws/fittss-law
https://www.nngroup.com/articles/fitts-law/
https://en.wikipedia.org/wiki/Fitts%27s_law#Implications_for_UI_design
@LGUG2Z commented on GitHub (Jan 23, 2025):
Komorebi and AltSnap now work well together so it's possible to alt+rightclick anywhere on a window to resize.
@igorcmoura commented on GitHub (May 13, 2025):
Thanks for the reply!
But I'm not sure I understand it. The issue is not about resizing a window, it's about being able to click on elements that are at the far end of a window when the mouse is at the border of the screen.
Here some examples:
Chrome Tabs
Without Komorebi
When Chrome is on fullscreen I can place my mouse at the border of the screen and the tab is clickable:
With Komorebi
When using Komorebi this doesn't happen:
I have to move my mouse 6px down to click on tabs:
VS Code Menus
Without Komorebi
Same thing happens on VisualStudio Code's menus when on fullscreen:
With Komorebi
Using Komorebi prevents me from being able to click on them when the mouse is at the border:
I have to move my mouse 8px down to click on menus:
To be fair this happens because windows are never fullscren when using komorebi. So maybe making a window fullscreen when it's the only window at the moment and the configured border is 0px would mitigate this problem.