Shortcut to switch between windows of current application doesn't work across VMs

[ghost]

Qubes OS version (e.g., R3.1):

R3.1

Affected TemplateVMs (e.g., fedora-23, if applicable):

All

---

Expected behavior:

Another window with the same application comes into focus, even if the other window is run by another VM.

Actual behavior:

Nothing happens.

Steps to reproduce the behavior:

1. Start [application] in [AppVM_1]
2. Start [application] in [AppVM_2]
3. Set focus on [application] in either [AppVM_1] or [AppVM_2]
4. Press Alt+`` orAlt+~` (the default key bindings in KDE)

General notes:

---

Related issues:

Relevant labels:

• Bug
• UX
• P: minor

[andrewdavidwong]

Generally, window classes in Qubes work differently than in standard KDE. Currently, by default, the window class is the domain. From that perspective, it makes sense that windows from the "same" application in two different VMs will not be treated as two windows from the same application. Arguably, they're not really (i.e., not merely) two windows from the same application. Rather, they're two windows from two instances of one application running in separate VMs. That's why I'm reticent to call this a bug. Depending on the UX approach, this may be a feature, not a bug. It may just be "the Qubes way."

[andrewdavidwong]

Generally, window classes in Qubes work differently than in standard KDE. Currently, by default, the window class is the domain. From that perspective, it makes sense that windows from the "same" application in two different VMs will not be treated as two windows from the same application. Arguably, they're not really (i.e., not merely) two windows from the same application. Rather, they're two windows from two instances of one application running in separate VMs. That's why I'm reticent to call this a bug. Depending on the UX approach, this may be a feature, not a bug. It may just be "the Qubes way."

[unman]

The statement of "expected behaviour" shows confusion.
If it is "Another window with the same application comes into focus", then the actual behaviour matches this.

As @andrewdavidwong says, following the steps given, they are two instances. I would say of different applications.
Insert Step 1a: Wait 10 minutes.
Then ask if these are the same application - When was app1 started? When app2?

[unman]

The statement of "expected behaviour" shows confusion.
If it is "Another window with the same application comes into focus", then the actual behaviour matches this.

As @andrewdavidwong says, following the steps given, they are two instances. I would say of different applications.
Insert Step 1a: Wait 10 minutes.
Then ask if these are the same application - When was app1 started? When app2?

[tasket]

This is less a bug than an idiosyncrasy of Qubes. The window manager examines each app as object references in its environment, so in dom0 the WM sees vms as the separate apps. If I run 2 firefox windows and a tbird window all in the same vm, then Alt-tilde switches between all of them.

IOW, the app 'name' isn't used and even if it were, you would get names like "personal" and "untrusted"; just vm names. The rest of the titlebar contents you see will often change depending on the document or address being used at the moment.

There is also a question of whether a window manager in Qubes should try to associate UI elements by app name. This can affect a user's view and workflow on their desktop depending on a claim by a domU app.

[tasket]

This is less a bug than an idiosyncrasy of Qubes. The window manager examines each app as object references in its environment, so in dom0 the WM sees vms as the separate apps. If I run 2 firefox windows and a tbird window all in the same vm, then Alt-tilde switches between all of them.

IOW, the app 'name' isn't used and even if it were, you would get names like "personal" and "untrusted"; just vm names. The rest of the titlebar contents you see will often change depending on the document or address being used at the moment.

There is also a question of whether a window manager in Qubes should try to associate UI elements by app name. This can affect a user's view and workflow on their desktop depending on a claim by a domU app.

[andrewdavidwong]

Closing as notanissue.

[andrewdavidwong]

Closing as notanissue.