Skip to main content
Inspiring
November 16, 2012

P: Can't cmd+tab to web browser (Chrome ver: 16.0.912.75) from CS6 (OSX/10.6.8)

  • November 16, 2012
  • 156 replies
  • 2373 views

When cmd+tabbing between Photoshop CS6 and Google Chrome, Photoshop document windows remain visual on top (but inactive). The web browser window is called up over other applications, but remains behind Photoshop. The problem seems to only happen when switching to Chrome.

Photoshop ver 13.0.1
Mac OSX ver. 10.6.8
Chrome ver: 16.0.912.75

This topic has been closed for replies.

156 replies

Participating Frequently
January 7, 2016
I reported the issue to google and have never heard anything back.
Inspiring
January 7, 2016
Any movement on this? It happens consistently to me. Also confirmed with 3 others on our design team.

CMD + Tab from Photoshop to Chrome switches the active application, but does not bring Chrome to front. Chrome shows in the Menu Bar, but Photoshop windows remains on the top layer.

OSX El Cap. 10.11.2 | Photoshop CC
Participating Frequently
January 7, 2016
Also having this issue switching between PS and Chrome

This has been happening on CC 2014 and 2015 on both OS 10.09 and 10.11

MacBook Pro (15-inch, Mid 2012)
Inspiring
January 1, 2016
Again, let Google know about this, so they can fix the Chrome bug soon.
Inspiring
January 1, 2016
Also having this issue
OS X 10.11.2
Model: MacBook Pro (Retina, 15-inch, Late 2013)
Photoshop: 20151209.r.327 x64, 2015.1.1 release

When I tab or switch using the dock to a web browser photoshop will stay active.
Inspiring
December 23, 2015
Ouch. That is going to make debugging more interesting for Google.
Participating Frequently
December 23, 2015
We observed that only OS X 10.11.2 computers are affected. We can't reproduce this behavior running OS X 10.10.5.
Participating Frequently
December 18, 2015
Thanks Chris - I have reported the issue to google. We shall have to wait and see.
Inspiring
December 18, 2015
Three people posting about this in one day after it's been gone for a year -- probably means that a Chrome update reintroduced the bug. Please let Chrome/Google know about this so they can fix it.
Participating Frequently
December 17, 2015
We have the same issue on our computers running OS X 10.11.2, Adobe Photoshop 16.1.1 (the Creative Cloud version) and Google Chrome version 47.0.2526.106 (64-bit).

Has somebody with similar configuration not that issue?

Thanks for any help!

Yann