Just a bit curious, I went looking for ways to find who has focus… It should be given - I think by the WM - by this command :
xprop -root _NET_ACTIVE_WINDOW ; done
All good in Dom0, but a quick test in an appVM gives “not found”.
This is not entirely surprising, because the WM is in Dom0, but I thought someone in the appVM would know.
I tried getting a list of all windows from xwininfo -root -all and running xprop on every window, using ‘-id’ parameter, but it seems that only the root window in Dom0 knows who has focus.
I am wondering if the problems are related to firefox not having the normal information it would normally get from the WM. I’ve noticed before that firefox does not work correctly with no Window Manager, so I am assuming that Qubes provides some kind of ‘stub’ or partial passthrough WM to windows on the VM display. Maybe this is something extra which is needed for this application… although I would have no idea how, and I expect there are may other things firefox & chrome could be asking for.
Anyway, maybe xprop, xwininfo and maybe wmctrl could help someone else to spot a root cause.
Hopefully, the new graphics stack dev will solve it… as it’s surely more complicated than anything I could imagine.