KDE: Double clicking on an "open" file (in the background) appears to do nothing

[bnvk]

I'm not sure if this relates to Qubes or if this is a KDE issue, but the scenario is:

• I have the file MyFile.txt open already by gedit, it's just in the background
• In foreground I have File Manager open
• Upon double clicking on the MyFile.txt nothing appears to happen

The correct behaviour should be to bring the already open file into the foreground, otherwise it is quite confusing and user may think the file is corrupt or cannot be opened.

[marmarek]

This is probably result of our GUI virtualization solution, which
(intentionally) passes only little subset of events/metadata to dom0.
For example I don't think VM is able to bring arbitrary window to front.
This needs some more though to prevent attacks like focus stealing...

Currently the only similar feature implemented is "demand attention"
flag. But I'm not sure how is that related to bringing existing editor
window to the front.

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[marmarek]

This is probably result of our GUI virtualization solution, which
(intentionally) passes only little subset of events/metadata to dom0.
For example I don't think VM is able to bring arbitrary window to front.
This needs some more though to prevent attacks like focus stealing...

Currently the only similar feature implemented is "demand attention"
flag. But I'm not sure how is that related to bringing existing editor
window to the front.

Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?