Still can't seem to use mailto handler - mailto links are not launching in this (stable) release. Canary works fine.
Can't reproduce that here. It's a problem on your system (e.g. xdg-open, if you're using DEless linux).
And of course meant to say 'xdg-email' because that's the mail handler.
I can't to see anything on YouTube after this update. 2-3 seconds of playback and stop. All playback controls are not availiable ((
I like to save sport pages in the night to read them next day, but almost everytime I try to save www.GSP.ro, chrome doesn't create the *.html file (it creates only the folder with saved files). I have to realod the page and keep trying to save it until the file is created.This bug happened since Chrome 13 or 14.
I also don't have the option to use the Gmail and Google Calendar protocol handler in this stable version. I tried in Windows 7 and Ubuntu 12.04. and Chrome is not asking me nothing about mailto and webcal, when I log into these two pages.Please fix this!
Why are their no updates to Android and iOS versions? Do they have all of the vunerablities as listed above? Or are they a different code base that gets less attention? Does your code bounty count for finding flaws in these browsers? Also, I'm typing this on a Samsung Galaxy Tab I get little red sqiggly lines when I have misspelled words but no way to access the dropdown for suggested correct spelling.
Chrome has an awful, awful bug which causes gdi objects to leak when the browser is open for extended periods of time. If there are a lot of tabs, it can hit the windows system limit and cause the system to behave erractically and sometimes freeze or crash windows and/or chrome. You can observe it by watching the gdi objects for each chrome process and over time it will go up from 200ish to over 1000 even with the same number of tabs and no new activity. Something is happening while the user is not interacting with the browser to cause these gdi leaks. Please have someone prioritize this fix. There are various bug reports, but it seems like very little movement. As a user, this is the most disruptive bug in chrome and it seems like it's not getting the attention it deserves to be fixed.
I can't find a way to get protocol handlers to work. The chrome://chrome/settings/handlers box is blank and there seems no way to add a handler to it.
I can't get the email protocol handler to work. The chrome://chrome/settings/handlers box is blank and there is no way to add to it.
Really good blog post, this is very similar to a site that I have. Please check it out sometime and feel free to leave me a comment on it and tell me what you think. I’m always looking for feedback
Post a Comment