Stop capitalizing, auto-correcting file names and paths? #2562
Replies: 2 comments 1 reply
-
|
@treebeard9 Thanks for reporting this Could you share the exact steps to reproduce? Just to confirm, where are you seeing the auto-correct pop up:
A screenshot (or short screen recording) would help a lot, especially showing the auto-correct UI (the little “x” you mentioned). I cant find it anywhere in the ui. We have a release scheduled in a few days, and if you can share the context soon, we should be able to get a fix into the next release. This definitely feels like a UX bug that shouldn’t happen. I haven’t been able to reproduce it on my Mac yet, so the extra details will really help. |
Beta Was this translation helpful? Give feedback.
-
|
Attached some recordings, 1 is a brackets recording to show the old behavior
1. Creating new file or renaming old filename — automatically capitalizes first letter and autocorrects filename
— in Brackets, I was able to save a file by seeing the finder window and never saw filenames forcing capitalization or auto-correcting words
2. While editing code in editor such as typing a filename, it autocorrects to a dictionary word instead of the actual path, its automatically filing in the word — which is great, I like this feature, but it’s not choosing the folder that’s in there
/uploads somehow becomes /uploaded
And thanks so much for responding so fast!!

… On Jan 6, 2026, at 10:50 PM, Arun Bose ***@***.***> wrote:
@treebeard9 <https://github.com/treebeard9> Thanks for reporting this
Could you share the exact steps to reproduce? Just to confirm, where are you seeing the auto-correct pop up:
When renaming/creating a file in the File Tree, or
While editing code in the editor (e.g., typing a path in CSS)?
A screenshot (or short screen recording) would help a lot, especially showing the auto-correct UI (the little “x” you mentioned). I cant find it anywhere in the ui.
We have a release scheduled in a few days, and if you can share the context soon, we should be able to get a fix into the next release. This definitely feels like a UX bug that shouldn’t happen. I haven’t been able to reproduce it on my Mac yet, so the extra details will really help.
—
Reply to this email directly, view it on GitHub <#2562 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIKZ2DWDPHXDV4V5RALE6I34FSNCVAVCNFSM6AAAAACQ36CRMKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBTGA4DGNA>.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
New file names keep auto-correcting to a known word and also capitalizing it, so I have to click the little x to close the autocorrect first.
Every time I add a file path to a css image that is in the "uploads" directory in my projects, it auto-corrects itself to "uploaded" so looks like /images/uploaded instead of /images/uploads/ - I know it's a silly issue but it's just my quirky naming.
Phoenix Code 4.0.3 on macOS Sequoia
Is there a way to fix these issues so it behaves like Brackets did?
Beta Was this translation helpful? Give feedback.
All reactions