should not do the expose effect if there is one instance only on this workspace

Bug #709112 reported by Sebastien Bacher
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Unity
Fix Released
Low
Unassigned
unity-2d
Fix Released
Medium
Ugo Riboni
unity (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: unity

Using unity 3.2.16 in natty:
* open a firefox instance on workspace1
* open a firefox instance on workspace2
* go to workspace one and click on the firefox launcher

What happens:
* the expose effect trigger with the one instance on that workspace

What should happen:
* nothing if firefox is already focussed on screen

Mirco Müller (macslow)
Changed in unity:
importance: Undecided → Low
Changed in unity (Ubuntu):
importance: Undecided → Low
Mirco Müller (macslow)
Changed in unity:
status: New → Confirmed
Revision history for this message
Mark Shuttleworth (sabdfl) wrote : Re: [Bug 709112] Re: should not do the expose effect if there is one instance only on this workspace

 status new

I'm not sure I agree. We generally want a consistent result for each
action. There are exceptions, but they need to be thought through
carefully. John Lea, cc'd, has coordinated the spread/switch discussions
on desktop unity, let's ask his comment before confirming this report.

Mark

Changed in unity (Ubuntu):
status: New → Triaged
Changed in unity:
status: Confirmed → New
Gord Allott (gordallott)
Changed in unity:
status: New → Confirmed
status: Confirmed → Triaged
Revision history for this message
John Lea (johnlea) wrote :

We have gone through a lot of iterations with this behavior, there is quite a complex set of trade-offs in the launcher/workspace interactions.

We have a prototype that covers *some* of these interactions, see https://chinstrap.canonical.com/~johnlea/1104spread/unity_workspaces.air

With regards to the question of what happens when a user clicks on a app icon in the launcher when there is one instance of the app open in each of the two workspaces the answer is that yes, nothing should happen if firefox is already focused in the current workspace

We had to go through a lot of iterations to reach this conclusion ;-)

Changed in unity-2d:
status: New → Triaged
importance: Undecided → Medium
Ugo Riboni (uriboni)
Changed in unity-2d:
assignee: nobody → Ugo Riboni (uriboni)
assignee: Ugo Riboni (uriboni) → nobody
status: Triaged → In Progress
assignee: nobody → Ugo Riboni (uriboni)
Changed in unity-2d:
milestone: none → 3.8
Revision history for this message
Ugo Riboni (uriboni) wrote :

I think this was actually already done in 3.6.
Please double check and reopen in case I'm wrong.

Changed in unity-2d:
status: In Progress → Fix Committed
status: Fix Committed → Fix Released
Revision history for this message
Bazon (bazonbloch) wrote :

See also https://bugs.launchpad.net/ayatana-design/+bug/689733 and https://bugs.launchpad.net/ayatana-design/+bug/683170 where the behaviour of launchers should generally be limited on the active workspace.

Revision history for this message
Andrea Azzarone (azzar1) wrote :

I'm using 14.04 right now and the bug has been already fixed.

Changed in unity:
status: Triaged → Fix Released
Changed in unity (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.