On Mon, 18 Sep 2006 15:15:37 +0200 (CEST) Viktor Griph <[EMAIL PROTECTED]> wrote:
> On Mon, 18 Sep 2006, Ralf Fassel wrote: > > > Suse 9.3, fvwm 2.5.10 and also in 2.5.18, firefox 1.5.0.6 > > > > I have 5 Desks set up, running firefox on one of them: > > > > Style "Firefox-bin" StartsOnDesk 2, SkipMapping > > > > This works fine: the desktop is not switched when firefox starts up. > > > > However, since a recent upgrade of firefox, whenever I open a new > > tab (not: window!) in firefox via "firefox -remote openURL(...)", > > the desktop switches to #2 where firefox runs. This is not what I > > want, the desktop should stay where it is. > > > > In earlier versions of firefox, this used to work: the desktop was > > not switched. > > > > How can I see what makes fvwm2 think it should switch the desktop > > now? Is there some verbose/debug mode availbale? > > > > firefox does *not* open a new window (even in that case it should > > not switch desks with the SkipMapping above in place)... > > > > When using e.g. the KDE window manager, the firefox icon in the > > taskbar starts blinking when I open the new tab, but the desktop is > > not switched. > > > > Look att UrgencyFunc in the manpage. It might be that firefox > (incorrectly) use the urgency hint when a new tab is opened. > In that case Destroying UrgencyFunc should stop the behavior, but you > might want to redefine it in some other way to maybe just ignore > firefox. Nope, it's certainly not that. I can't even reproduce this, and I have the same version of Firefox as listed. The only thing I can think of is if something like FvwmEvent (perhaps listening on 'visible_name') is somehow causing it. It would be nice to get some feedback on this -- since Firefox has been the cause of many issues in the past, not least of which were down to itself and not a cause of the window manager. Chances are this is exactly the same. :) -- Thomas Adam
