If you’ve been using Google Chrome recently, and for Windows users I don’t see a reason why you shouldn’t minimally at least, you may have noticed the problem when you try to save an image with a different than current image name. Problem is, if you rename the image to say “Mars” and click save, it will get saved as the image name, concatenated to the file extension without the dot separator, e.g. “Marsjpg”, which ofcourse would forbid you from automatic Image opening with default Image Browser.
Now this is a known bug that’s been reported since Sept 4th, and it’s still marked as Uncofirmed. I’m not sure why such a simple obvious bug is taking so long. Perhaps Google was depending too much on open source developers help, not sure. But 1 month is long enough to confirm an obvious issue. Those delays would make people lose faith in Chrome, and stop taking time reporting future problems.
Since the bug seems to take long to fix, the quick and simple work around for you and me is to write the full image name with extension, “Mars.jpg”
I can just imagine the developer working late at night to finish the Save Image As feature, and he goes something like return file_name && file_extension, forgetting the dot separator. Perhaps a refreshing Pepsi would do. Works for me :).