Open brabalan opened 11 years ago
Not known, since I don't use firefox. I would assume it doesn't support the accessibility api
I can confirm this (FF 16 and 19)
So I figured out why this happens. Firefox doesn't respond to accessibility requests until a little while after it launches. By which time xnomad has already given up on it. For now you can get around this by launching xnomad after firefox. That seems to work here.
i can support fjolnirs' last comment: if firefox is launched after xnomad, it is not managed by the window manager, when you start firefox before, its windows are managed nicely.
It seems that Firefox is not controlled by xnomad. Is this a (known) bug?