New windows always appear in the space in which the application was launched

VERIFIED INVALID

Status

VERIFIED INVALID
11 years ago
11 years ago

People

(Reporter: jonathan.hume, Unassigned)

Tracking

Details

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.12) Gecko/20080206 Camino/1.5.5
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.12) Gecko/20080206 Camino/1.5.5

When multiple Camino windows are open across multiple desktops/spaces, opening a new window, regardless of what desktop you are on, results in window appearing on the desktop from which you launched Camino and the desktop focus being shifted back to that desktop.

Reproducible: Always

Steps to Reproduce:
1.Configure OSX 10.5 with more than one space/desktop
2.Start Camino on one of the desktops.
3.Open a second Camino window on that desktop and drag it onto one of the other desktops you've got.
4.On this other desktop, select Camino and open a new window. 


Actual Results:  
It shifts the desktop focus back to the original desktop from which Camino was launched and opens the new window there.

Expected Results:  
It should open the new window in the same desktop (as would be expected and is the  current behaviour for Firefox 3 RC3 and Safari).

Comment 1

11 years ago
Apple provides absolutely no API for apps to understand or interact with Spaces, so not only are we not explicitly causing this, we couldn't change the behavior even if we wanted to.

Either you have set Camino to be pinned to a space in the Spaces preferences, or you are encountering a bug in Space itself that would need to be reported to Apple. (I haven't seen the same behavior on any of my Leopard machines, so I would guess that the former is more likely.)
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INVALID
(Reporter)

Comment 2

11 years ago
Doh, pinned it in spaces,  sincere apologies for false alarm.

Updated

11 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.