Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Window exception that is not based on the title #1644

Open
bashfulrobot opened this issue Jul 19, 2023 · 3 comments
Open

Window exception that is not based on the title #1644

bashfulrobot opened this issue Jul 19, 2023 · 3 comments

Comments

@bashfulrobot
Copy link

bashfulrobot commented Jul 19, 2023

This is not a bug but rather a question.

Currently, in the config.json for window exceptions, it seems to use the app name for the class, and then use the window title.

IE (generated using the GUI)

{
  "float": [
    {
      "class": "pop-shell-example",
      "title": "pop-shell-example"
    },
    {
      "class": "zoom",
      "disabled": true
    },
    {
      "class": "Brave-browser",
      "title": "test alert"
    }
  ],
  "skiptaskbarhidden": [],
  "log_on_focus": false
}

In my use case, I use a browser extension with my calendar, and the windows are the notifications (additional features from the in-system notifications). However, the window title reflects the name of the event name - which will obviously be different for each one.

Any suggestions here?

Thank you.

@mmstick
Copy link
Member

mmstick commented Jul 19, 2023

Exceptions may be defined by wm_class and/or wm_title. Regular expressions are supported in the config file. Some of the default rules are using them.

Most web browsers usually don't have a wm_class defined on their dialogs, so we auto-exclude windows without that property set.

I do recall that we added rule for Firefox so that its developer tools window would float by default.

@bashfulrobot
Copy link
Author

Thanks for the info! I think I am skunked as the window title is literally the event title, and no common pattern to match.

I guess we can close this off unless you want to track it for some purpose.

@mmstick
Copy link
Member

mmstick commented Jul 20, 2023

Perhaps it's worth patching the extension to set a more descriptive title or class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants