Inconsistent behaviour shift or ctrl click in unfocussed nautilus window

[Colin Law]

Problem 1, to replicate
Open nautilus and another window (I used terminal but I think any will do), with both visible on display.
Select List View in nautilus
Click to select a file or folder
Click in the other application's window
Ctrl Click another file/folder in unfocussed nautilus window

Expected behaviour: The file should be selected and nautilus should receive the focus
Actual behaviour: The file is selected but nautilus does *not* receive the focus.

Problem 2, to replicate
As above but Shift Click in unfocussed nautilus window

Expected behaviour: Files should be selected and nautilus should receive the focus
Actual behaviour: Nothing happens at all

Problem 3, to replicate
As problem 2 but with nautilus in Icon View.

Expected behaviour: Files should be selected and nautilus should receive the focus
Actual behaviour: Files are selected but nautilus does not receive the focus

A simple click in nautilus when unfocussed has the expected effect of selecting the clicked item and giving nautilus the focus.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.2.1-2ubuntu12
ProcVersionSignature: Ubuntu 3.2.0-11.19-generic 3.2.1
Uname: Linux 3.2.0-11-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Fri Jan 27 15:09:31 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Colin Law (colin-law)]

Following further tests I realise that this problem only appears when running Unity-2. All operates as expected when running 3d. I guess that this means it is not an upstream problem.