P: Save As - the focus is not in the file name field - macOS Monterey

Are you using an operating system before Monterey that has problems with filename during save?

For me and probably others, this would mean buying a new computer, so it's not really a solution for many. An otherwise working older iMac can't be upgraded past 11. 

Hi @bdub11059173, sorry this fix didn't solve your issue.

Could you share a screenshot of what you are seeing? It is possible this is another issue and the team can look into this further.

Thank you,

12.3.1 and this is still not working correctly!

Since one of the last updates (not exactly sure which), when I use "save for web" and try to type in a file name to save, the file extension (i.e. JPG or PNG) is auto-added after every letter I try to type, also moving the cursor to the end of the extension, so i have to keep moving the cursor back to type another letter or delete everything and start over every time I try to save the file.  

It's extremely agressive too, adding the extension back even as I try to delete one space, so I end up with multiple instances of the extension jumbled up in the new filename as I type.

MAC OS 12.0.1, Macbook Pro, Photoshop 23.3.1

I'm running the latest macOS 12.3.1 and Photoshop 23.3.1 and still have this issue. Doing a normal Save-As or Export-As works properly with just the file name selected, but the Save for Web dialog is still selecting the entire file name and extension by default. I just jumped from Mojave straight to 12.3.1 last week so I couldn't say if it worked correctly in 12.1.

The Save for Web file-save dialog box will also always appear touching the bottom left of the screen instead of center. And if you click on the arrow to hide the column view finder path, the next time you get to this screen most of the dialog box will be hidden off the edge of the bottom of the screen. Re-opening the column view will just expand it further off screen.

Awesome, thanks for the feedback!

Regards,

Mohit

Since updating to 12.1 Monterey, mine is working fine too.  The problem has been resolved.

Yes, indeed fixed.