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

Artist666
Known Participant
February 8, 2016
maybe you guys from adobe can talk to google? my daily workflow with photoshop and chrome is very disturbed by this bug! 
Inspiring
February 8, 2016
very annoying!!!
jshhrrsn
Participating Frequently
February 5, 2016
@43542 Stevenson Hmm, there seems to be no "report troll" facility on here. Shame.
Inspiring
January 28, 2016
Same problem 😞 so frustrating
jshhrrsn
Participating Frequently
January 27, 2016
I've reported this to Google Chrome and it's looks like they've taken notice.

Add your voice to the thread here:
https://productforums.google.com/foru...
Inspiring
January 26, 2016
Oh, my fault, i mean it remains in v47.
Inspiring
January 25, 2016
Thanks, Anton. As temporary workaround fixes go, using Chromium 45 feels less hacky/frustrating than [a] switching to Safari or [b] using a freeware alternative app switcher (all of which were buggy).

To anyone else who, like me, is delving into Chrome dev builds for the first time as a result of this advice: As of today (Jan 25), really do use Anton's recommended version up there (45.0.2454.101). Even though he observes that the bug "left in v47", it seems to be back in full force as of the v50 releases of Chromium / Canary.
Artist666
Known Participant
January 25, 2016
thanks Anton,
that would prove, that chrome is the issue.
and in 48 it isnt fixed as well.
Inspiring
January 25, 2016
Hey, mates, looks like installing latest of 45 chrominium version (45.0.2454.101 (64-bit) solves the problem. It dates back to september, but this is the only trick i found to stay with my chrome addons. Hope that helps until they fix chrome.

p.s. bug comes in v46 and left in v47 (111 is last one, so you could free up yourself from checking)
http://sourceforge.net/projects/osxpo...

Nice day to ya all, ninjas!
Inspiring
January 22, 2016
See above - it is very specific to Chrome, and they've had similar issues before.