You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is when using Miriway 24.11, and there are several parts:
Chromium creates a notification window (why doesn't it use swayync?);
this window gets raised (how? xdg-activation?); and,
Miriway responds to the raise by (potentially) switching workspaces.
I am not sure if this is Mir, or Miriway at fault as I've not traced how the raise request is validated. But Chromium shouldn't be able to use xdg-activation when it doesn't have focus.
To reproduce (in Miriway):
When chromium is about to pop up a notification, switch to any other workspace.
Expect: focus to remain on the active window in the current workspace
Actual: focus moves to Chromium in its workspace
The text was updated successfully, but these errors were encountered:
This is when using Miriway 24.11, and there are several parts:
I am not sure if this is Mir, or Miriway at fault as I've not traced how the raise request is validated. But Chromium shouldn't be able to use xdg-activation when it doesn't have focus.
To reproduce (in Miriway):
When chromium is about to pop up a notification, switch to any other workspace.
Expect: focus to remain on the active window in the current workspace
Actual: focus moves to Chromium in its workspace
The text was updated successfully, but these errors were encountered: