Thanks again Google Dev Team! :)
is that all with the settings page?
My problem (http://code.google.com/p/chromium/issues/detail?id=112444) still exists :-)So problem with NTLM proxies.
i used to be able to find this pagehttp://googlechromereleases.blogspot.com/by hitting F1 and then it was close to left bottom but i dont see that anybody.Please put it back there.
When are we getting the master password for our saved passwords?
Also still having the crashing issue referenced in http://code.google.com/p/chromium/issues/detail?id=112444 Please provide instructions on how to actually get Chrome to startup and update itself.
We can't use Chrome Web Store: http://code.google.com/p/chromium/issues/detail?id=106095
For those asking about the redesigned options page, see Issue 100885.The "Uber Page" will include more chrome://x pages (ex: history) and will not be released in M18 Stable.
Is it just me or does each release seem to hog more memory and also manage memory worse?I'm now using ~700mb just for the new tab screen. Memory doesn't seem to get released back to the OS efficiently when tabs are closed. If I open gmail, gdocs & 1 bank website, things slow to a crawl and sometimes doen't ever recover so I'm left with no choice but reboot.Things have gotten so bad, that I think I may just head back to the beta release, something I haven't done since I received my Samsung Chromebook 2 days before they went on sale last year :(
@MarcFully agreed on the memory usage. Chrome team, what are you even doing? The browser was perfectly fine months ago, the only area where improvement is needed is the UI.
the quality of these dev builds has drown recentlyyou keep introducing bugs and scaring us with shitty modifications like the options pageSTOP WASTING TIME and implement missing MAJOR features already, like master password, ability to not collect history but keep cookies, and others.look em up at http://www.google.mw/support/forum/p/Chrome/thread?tid=197b83f4f38c69cf&hl=en&fid=197b83f4f38c69cf000486e05ffe99a9&hltp=2
please fix this issue. (http://code.google.com/p/chromium/issues/detail?id=100021)it has been there since chrome 15 beta until the latest chrome 19 canary.
Post a Comment