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 :).
Popularity: 29% [?]
A developer has his days where he sets tough targets and miletones to deliver. Tonight was such a night for me. I had windows open all over, working on multiple things simultaneously. I did a small update to one of my sites in the header, tested fine, upload to production. Only to find out all of a sudden, the page magically refreshes everytime I click on the search textbox field!
I know what you’re thinking. OnClick events. I tried to check them all, even though I did not made any modifications there. There was absolutely nothing wrong with them. I revised all the header parameters. No refresh or anything as that. Is my site hacked or something? No. Problem replicated in development local machine. I have a load of javascript files for jQuery and autocompletion, so I thought to my self, maybe a new version of Firefox & Chrome is creating this sort of problems with an old jQuery library, as IE this time was on the safe side!. Googling for similar instances, no results!
I placed another test textbox, it absorbs the same behavior. Any other page on the site does not have this problem but the main page. Something must be wrong. I had to make the bad move. I started trimming the code to pieces. First, remove all HEAD section. Problem remains. Remove footer, all javascript code, remove the whole body. Problem only went when I replaced the whole page with single input box inside BODY tag. Now, start revirsing and building up the site. Once I added the header section, problem comes again! I only replaced the image for God’s sake!
<span><a href=”index.php” ><img src=”logo.gif”/></a></span>
Darn it! I only forgot to close the <a> tag, and the text boxes turned into monster linking creatures! Wonder why only the textboxes absorbed the links though. Hahh… night wasted, but at least I will sleep with peace of mind.
Popularity: 17% [?]
