Bug 231334

Summary: metacity shouldn't switch display for startup-notification
Product: [openSUSE] openSUSE 11.0 Reporter: Wolfgang Rosenauer <wolfgang>
Component: GNOMEAssignee: E-mail List <gnome-bugs>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P3 - Medium CC: kontakt, vuntz
Version: Factory   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard: gnome-usability,gnome-wrong-out-of-the-box, gnomeup-metacity
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Wolfgang Rosenauer 2007-01-02 19:46:50 UTC 
What annoys me in Gnome's metacity is, that since Firefox supports startup-notification every click to a link moves the complete Firefox window to the current display if it is on another one first.
I think that's always a bad idea.

Windowmaker for instance does nothing (what is my favourite)

compiz goes to the viewport where Firefox lives instead moving Firefox to the current viewport which is justifiable.
It would be ok to open a new window on the current location but if Firefox opens a tab it shouldn't be moved.
Comment 2 Wolfgang Rosenauer 2007-08-29 17:07:51 UTC 
What about this very old enhancement request?
Comment 3 Mark Gordon 2007-08-29 20:59:07 UTC 
This issue (with various proposed solutions) is discussed upstream at http://bugzilla.gnome.org/show_bug.cgi?id=307693

Given that we don't have anyone internally hacking on metacity, it's probably most appropriate to have upstream handle this.  Resolving LATER.
Comment 4 Wolfgang Rosenauer 2007-10-19 20:22:04 UTC 
Currently some discussion is going on on another Gnome bug about that issue:
http://bugzilla.gnome.org/show_bug.cgi?id=482354

Maybe time to investigate again.
Comment 6 Wolfgang Rosenauer 2008-04-01 08:40:22 UTC 
move to next release
Comment 7 JP Rosevear 2008-04-01 13:01:35 UTC 
I believe this behavior is part of the window manager spec.
Comment 8 Wolfgang Rosenauer 2008-04-01 13:21:55 UTC 
(In reply to comment #7 from JP Rosevear)
> I believe this behavior is part of the window manager spec.

Have you read the upstream bug in comment #4?
That doesn't look like desired behaviour.
Comment 9 Lubos Lunak 2008-04-01 14:36:30 UTC 
I'm not sure I understand exactly this issue (and the upstream report is huge), but I don't think this is specified by the spec. There is either a bug in Mozilla in how it handles opening the page or in Metacity in how it handles the request from Mozilla.
Comment 10 Wolfgang Rosenauer 2009-09-29 17:50:04 UTC 
And finally...
Fixed in 11.2
Comment 11 Wolfgang Rosenauer 2009-09-29 17:51:17 UTC 
Hopefully not just because startup-notification support of FF is a bit broken but the upstream bug has been resolved so I'm just guessing it's all good now.