mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: Window is managed despite ignore rule #534
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 @gazpachoking on GitHub (Nov 26, 2024).
Summary
I'm trying to add an ignore rule so that the bitwarden password popup from ms edge is not managed. The rule seems to match, but for some reason the window still gets managed. Doing a retile doesn't exclude the window.

Version Information
Komorebi Configuration
Hotkey Configuration
Don't think this is relevant here.
Output of komorebic check
KOMOREBI_CONFIG_HOME detected: c:\Users\chase.sterling.config\komorebi
Looking for configuration files in c:\Users\chase.sterling.config\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\chase.sterling.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
@gazpachoking commented on GitHub (Nov 26, 2024):
If I stop and start komorebi with the window open, the window is properly ignored.
@alex-ds13 commented on GitHub (Nov 27, 2024):
My guess would be that when that window first opens it starts with a different title, so it gets handled then it updates its title... Can you use
winspy++or the AHK spy utility to check if that window has any other way of identifying it, like a specific class?You can also check the logs for when you open that window (or open a terminal and run
komorebic logto see them real time..) and try to see what is the title it starts with, it might have something like "Extension" on it that you can try to use... If you need help you can try to share the logs here so we can help pinpoint that.But your best bet would checking for a specific window class...
@gazpachoking commented on GitHub (Nov 27, 2024):
I checked the class, it's the same as the main Edge window, so no luck there. I also tried adding edge to the
object_name_change_applications, which didn't help either. I tried windowspy++, but I don't know how I can capture what title the window was created with.I then watched the komorebi log, and could indeed see that the window was created with a title like
_crx__toheunteuohnoentuoenh(I'll note, the only way I can see that in the log is if I have my ignore rule in for theBitwardentitle. Without that rule I don't see any log messages about that title.) I added the ignore rule for title starting with_crx__and it started working as expected. I also saw the name change in there, I'm not aware enough of the internals to be able to tell why it doesn't work with the final title whenobject_name_change_applicationsis defined.@alex-ds13 Thanks for the pointer that it might be changing the title after creation, that's what lead me to the solution!
I don't really know if this rule is something that would be suitable for the application specific rules, since I have no idea what other windows edge might create with that title prefix.
@alex-ds13 commented on GitHub (Nov 27, 2024):
object_name_change_applicationsis for applications that don't emit aShowevent at the start and simply emit a title change event. This is not the case since that window is emitting aShowevent at the start, it simply has a different title than you thought of. So I wouldn't add it to that rule...I would probably Google if that name is normally used by extensions' windows on chromium browsers, if it is it would be safe to add it to the ASC.
@alex-ds13 commented on GitHub (Nov 27, 2024):
So from what I've quickly searched,
.crxis the extension given to chrome extensions. So it makes sense that a chromium browser extension first opens with that title. Considering this I think it would be ok to add either ignore rules or floating_window rules to theApplication Specific Configurationon its github, for any window with title that starts with_crx__, this way it would be applied to any chromium browser. That is assuming that extension windows should be floating and not tiled, which to me seems a fairly reasonable assumption!@LGUG2Z What do you think? ^
P.S. This issue can probably be closed since this is not a bug and has been solved...
@LGUG2Z commented on GitHub (Nov 27, 2024):
Yeah I think this is good to close, but if someone wants to add a blurb about this on the docs site somewhere they can reference this issue number.
@LGUG2Z commented on GitHub (Nov 27, 2024):
Ah I thought this was familiar, it came up in relation to Chrome on the Discord a while ago: https://discord.com/channels/898554690126630914/898556726108901386/1231384330790633482
I think we can add default rules for all Chromium based browsers and popup extensions to the asc ^