
I remember asking a while back about Firefox imposing a switch of workspaces when I opened a link via another program on another workspace, and got a response that it was the fault of Firefox for doing something it shouldn't. I can't remember more than that, I'm afraid, having long since stopped using Firefox! For the details, you might want to search the archives. On 15:31, Fri 28 Dec 2012, Brandon Allbery wrote:
Date: Fri, 28 Dec 2012 15:31:55 -0500 From: Brandon Allbery
Subject: Re: [xmonad] Window gets pulled into another workspace To: adam vogt , Xmonad Mailing List List-Id: "xmonad: a tiling window manager" On Fri, Dec 28, 2012 at 2:05 PM, Raghavendra D Prabhu < raghu.prabhu13@gmail.com> wrote:
I have manageHooks in place; in this case, the manageHook is for terminal to be on workspace B and firefox on workspace A and somehow the terminal gets pulled into workspace B. Note that this doesn't only happen with windows with manageHooks but any active window. To reproduce this, create a request to make a window in a time-delayed fashion, best way is to start firefox download for a busy site (or just enough for you to move to other workspace).
But I tend to do this somewhat regularly, and don't see this.
EXCEPT: if I'm using xcompmgr, which seems to get confused in this and similar cases. (If you use a compositing manager, it draws and positions all actual windows; an application "window" exists but is never mapped. Compositing in X is rather hacky.) Are you using xcompmgr, by any chance?
I have heard that compton fixes this issue with xcompmgr, but have not been able to verify.
-- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad