Comment #65 on issue 812 by estmatic: Profile/login support http://code.google.com/p/chromium/issues/detail?id=812
Comment 39 states that they'll look at implementing this only if they get a good ui, and that they have other features as a priority. The problem, to me, is that they've merged what are actually two separate issues. One is support for multiple profiles (which is the original issue) and the other is a master password (about 4 requests for that have been merged with this issue). The last 15 or so comments are all talking specifically about the master password with no mention of profiles. I for one have no need/desire for multiple profiles in my browser. I don't use them in Firefox and I wouldn't use them in Chrome. I do very much want a master password though. I understand that implementing the profile feature could also take care of the master password concern, but to me the master password should have a much higher priority. It should be implemented regardless of when/if profile support is added. I'm not saying there aren't any, but I can't think of any other program that lets you view passwords in plain text without some sort of authentication (or at least the option). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
