P: Arrow keys stop working in type tool / text in CC

Howdy Timo,

Sorry for the delay in getting back to you.

Yes, your steps are perfect and I can now reproduce the problem. I've gone ahead and logged a bug against this.

Thanks much for your steps and sorry for the trouble this error has caused,
David

Having the same problem, it occurs randomly from time to time.

Photoshop CC 2014.2.2
Mac OS X Yosemite 10.10.2
MacBook Pro with external Apple keyboard

>> Timo Mämecke wrote:
>> Simply deselecting View > Application Frame and selecting it again seems to do the trick, too

Yep, this 'hack' helps.

Timo, thanks. I can reproduce with those steps. I'll work with David to log a bug.

Addition:

Let's assume the arrow keys don't work anymore because I clicked on the Application Frame.

Deactivating and activating the Application Frame is not the only solution to make the keys work again. It kinda work's vice versa.

So when I change focus to another window and back into Photoshop without clicking somewhere on the Application Frame, e.g. with clicking on the Photoshop Icon in the App Bar, the arrow keys will work again.

To clear all confusions, here's what I do:

0. Application Frame is activated. New Document, make Text with Text Tool, arrow keys will work.
1. Change focus to another window.
2. Change focus back to Photoshop with clicking a Panel/Window in the Application Frame of Photoshop. I like to click the Navigator, but it works with every Panel.
3. Select Text with Text Tool, arrow keys won't work.
----
4. Change focus to another window.
5. Change focus back to Photoshop with clicking into the open document or with clicking the App Icon.
6. Select Text with Text Tool, arrow keys work again.

Hi David,

It seems like I overlooked something. I just encountered something new:

Interacting with another windows input text is _not_ causing the bug. Instead it happens every time when I change the application focus out of Photoshop and change the focus back into Photoshop with clicking somewhere on the Application Frame. So for example I click the Layers Panel, or the Navigator, or the Tools section, to change my focus back to Photoshop.
It won't happen when I change the focus back into Photoshop with clicking the Photoshop Icon in the App Bar or clicking into the empty space of a document.

Sorry for confusing you with the Chrome Input thing – it just worked every time because I change focus back into Photoshop with clicking on the Navigator. It's an habit.

If I can help fixing this bug with a screenshare, I'd love to help you.

Best
Timo

Thank you for your complete and detailed response. I was frustrated earlier because it seemed like this was a nonissue based on the responses that have been posted. Thanks again.

I've tried looking into this bug several times.  I was working on this just yesterday, in fact.

I cannot reproduce it using either the shipping or development versions of Photoshop on Mac OS 10.10 or 10.9.  

My machines are, admittedly, very "clean" -- that is, they have very little additional software installed other than Photoshop and, sometimes, other applications such as Illustrator, InDesign, Acrobat, Firefox, Chrome, etc.  My hardware is all standard -- keyboard and mouse, but no tablets and nothing "fancy."  In this configuration, I cannot reproduce the bug you are describing or any problem with the arrow keys and text.  That doesn't mean that I don't believe there's a problem, only that that I do not believe it's is caused by Photoshop alone -- there CLEARLY is some sort of interaction going on here that causes the arrow keys to fail.

Jeff is totally right -- this problem might have similar effects to the previous bug, but that one was reproducible AND solved several years ago.  This one still lacks a "smoking gun" needed to figure out the cause.  I will again ask people with this problem to:
 
   a) supply as much detail as possible about their setup and what they were doing during the session that caused the bug.  If this really is a simple or frequent bug, it should be fairly quick and easy to reproduce from launch, right?  Please share this information, so I can try and track down the cause.  What Timo did, above, was awesome and is tremendously helpful.  Unfortunately, this does NOT cause my system to hiccup.

   b) I will again offer to do a web-hosted screenshare with anyone having this problem in order to try to diagnose your system, application, etc.  This is free, safe, and easy.  I do it with users LITERALLY all over the globe, every week.  All you need is an internet connection, a phone line (the call is toll-free in most countries), and you might have to install an Adobe browser plugin.

We really do want to solve this issue, but without detailed clues, it's darn near impossible to solve.

Thanks,
David

I'm not embarrassed about anything, but you can't swear on this site. Like I said, the original issue that was 100% reproducible with consistent steps was fixed. We'll need consistent steps to reproduce to try and fix this issue.

And now you looked for a reason to remove my comment to hide your embarrassment. Wow. Really?

Bullsh*t. I posted here 6 months ago and still run into this bug. -_-