P: Arrow key's stop working in type tool / text in CS6

Since installing CS6, I've been working with the dashboard bkg as the entire screen. The only floating palette I have been using is the Kuler extension (for maybe two weeks max) simply because I can't find a satisfactory place to anchor it (I'm kind of a neat freak). I'll try anchoring that palette, and see if that helps.

Most of the time, the apps running in my background are Suitcase Fusion 4 (always), Bridge, Quark 9, and sometimes Safari, iTunes, and a Prynergy workflow system.

I'm curious to see how many of you setup CS6 similarly to CS5. Meaning, do you guys shrink the main dashboard background and have your tools/pallettes floating, with other apps visible in the background?

I ran into the keyboard problems many times, and it seems the only way I can fix it is through switching from one app and back to Photoshop. However, the same problem keeps happening.

Then, I decided to try and use CS6 as it was intended with the dashboard background encompassing the entire screen, which makes you only focus on your photoshop canvases. This seems to have fix the keyboard problem so far. Will report if anything comes up.

I am running CS6 with OSX 10.8.2
My Mac Pro has a 2.8 GHz Quad Core processor
and 2 GB memory.

I have the same problem, but am finding it seems to be happening when I have Safari open in the background. If I quit Safari, my cursor behaves itself again.

This isn't an ideal solution, but it does work.

yes thanks Louie, clicking font-size field again and back to text box also works

Yes, this is what's happening with my version. Except I don't have to click away from photoshop.

I found that by clicking on the font-size text field in either the character palette or the options bar then clicking back to my text box also fixes the issue.

Pressing 'Enter' from the font-size field is what's been breaking it consistently for me.

@615780 Harvey: YES

exactly... one important thing I'd like to point out about this that may help Adobe to hone in on this bug is that you need to press 'Enter' while the font size field is still selected. for instance you select some text, click on the font size field, and then hit the up arrow a few times to increase font size.

now at this point if i simply click on the text somewhere to deselect first and THEN commit changes everything is fine. BUT, if i hit enter while immediately after changing font sizes, while the font size field is still active, that is when the arrow keys (among other things) will lock up.

at this point the only thing to do is to switch to another app and back to photoshop and voila, everything is fine.

These steps reproduced on a Macbook Pro, early 2008, running 10.8.2.

How are things progressing with a fix for this? I also find that the same issue applies to using the delete key, but not the backspace key (which stupidly on my Mac keyboard is also called Delete... genius) - I mean the one that deletes ahead of the cursor, next to the end key.

I can reliably reproduce the issue, then fix it, every time by doing the following steps:
1. Go into a text box, select all the text, then change something such as the font size, line height, or any character value.
2. Hit Enter to commit the text changes.
3. Click back into the text box. Cannot use arrow keys.
4. Exit the text box (esc)
5. Click out of Photoshop, into another app, Chrome for instance.
6. Go back into Photoshop, can click into text box and use arrow keys ok.

Whenever I am editing text in Photoshop CS6, my arrow keys do not work. I cannot move the text cursor around the text with my arrow keys. This starting to bug me a lot and I would like to know why it doesn't work, or how to fix it. They worked fine in CS5, it was since I updated to CS6 that they no longer work properly.

Having same issue since CS6, using Creative Cloud on OS X 10.8.2 - MBP Retina. Hopefully it will be worked out soon.

Could you share some more specific examples of how you get this problem? Does it happen reliably? What other apps do you have running at the same time? If you have an easily reproducible case, I'd love to see it and can set up a connect session via the Internet to do so.

We do want to get to the bottom of this, but like Chris said, we can't fix what we can't see.

Thanks,
David