Ever since the last update to Brave (also with Chrome), I can no longer see the .jpg (et al) file extension types when downloading a file (ie, the file “Picture.jpg” only shows as “Picture” and “Website.html” is only “Website”).
The download window will also NOT show (1) or (2) at the end of the file name if I’ve already downloaded it.
I have found no way to get the file type extensions back. What happened and how do I fix it?
Version 1.34.81 Chromium: 97.0.4692.99 (Official Build) (x86_64)
I’ve been looking for answers to this problem for days, It’s driving me crazy. I guess the only option is to hope that this issue is remedied in the next update.
@rgnestle and @ThePaddyDuke I’m not sure what issue you both are having. I just went over to my computer and downloaded a picture. It showed up as JPG everywhere I looked.
Can you try to explain in greater detail what you’re missing? Because it shows up everywhere for me. I’m trying to figure out if your set-up is different, if I’m misunderstanding what you’re mentioning, or what?
This “Save As” box would normally read “this_cat.jpg” The “.jpg” file type (or any other types) used to show at the end of the file name when saving a file or Web page. Now it shows up with a hidden extension, but only in the browser, not in Finder. Also, when saving a file that was already saved, it used to append the name with (1) or (2) etc, but now it just shows the “A file with this name already exists” prompt and I have to append the file manually. Any ideas? Thank you!
@rgnestle Bah, I could swear I ended up on your post with a Windows tag but now am seeing Mac OS. I must have overlooked. When you showed the image for where “Save As” and “Tag” showed, it stumped me as it was a different look.
I went to research and I found that people started talking about this as an issue in a recent version of Chrome. I do believe this matches what you’re saying
https://bugs.chromium.org/p/chromium/issues/detail?id=1281406
If so, definitely have to hope @Mattches can pass it along or let us know if it’s a work in progress.
Thank you. Yes, I did see and mention that it was doing it in Chrome too. I did not know if it was coincidental or if it was a Chromium issue in general. I hope they fix it soon. It will save me some time. Thanks again for your reply!
This does appear to be a known Chromium issue that we will have to wait for an upstream fix to resolve. Appreciate your patience.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
