Canvas Size dialog rejects comma as decimal separator

3 replies
34 views
Translate

Hi Adobe Team,

I am using Photoshop version 27.10.0 on macOS, and the fact that the Canvas Size dialog no longer accepts a comma (,) as a decimal separator is severely breaking my daily workflow.

I am used to typing a comma for decimals, and in older versions of Photoshop, the app was smart enough to accept both commas and periods seamlessly. Since the modern UI update, Photoshop completely rejects or ignores the comma, forcing an unnatural change to my muscle memory just for this dialog box.

Interestingly, Adobe Illustrator still handles this perfectly, accepting both commas and periods without any issues. Photoshop should maintain consistency with other Creative Cloud apps.

This is a major regression in usability for international users. Please restore the previous behavior where both commas and periods were accepted as decimal separators.

Thank you.

D Fosse

Community Expert

What language version are you using?

I’m Norwegian, where comma is the standard separator, but I have always used the US English Photoshop version. I discovered a very long time ago that Photoshop didn’t like comma, but wanted a period. So I just adapted, started typing period, and very quickly I stopped even thinking about it.

I don’t know your workflow. To me, it was a very minor adjustment. On the other hand, if you routinely copy/paste from sources where a comma is used, I can understand the problem.

Translate

P

paulab82507932Author

Participant

Hi D Fosse. I understand you were able to adapt, but my post is highlighting a recent UI regression, not an inability to type a period. The main issue is the lack of consistency across the Adobe ecosystem. As I mentioned, the comma worked seamlessly in older Photoshop versions and continues to work perfectly in Adobe Illustrator today. When jumping back and forth between Creative Cloud apps all day, users shouldn't have to memorize which specific app supports standard regional formatting. It's an objective UX regression that breaks localization standards and disrupts professional workflows.

Translate

D Fosse

Community Expert

OK, not trying to argue. What I am saying is that this may be dependent on language version - and if this has indeed changed in the US English language version, that happened a very long time ago. It has been many years, at least 6 or 7 years and probably longer, since I first noticed this.

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.