On Mon, Mar 10, 2008 at 9:02 AM, Aric Guite <[EMAIL PROTECTED]> wrote: > The problem with all of this is that it is not (from my perspective as > an end user) expected behavior.
Then Safari isn't explaining their reset option adequately, and you should file a bug with Apple about either changing the behavior, or explaining it better. The site is http://bugreport.apple.com (you'll need to create a free account). > losing my Camino passwords when I reset Safari but not losing my > Safari passwords when I reset Camino is a problem. We could make Camino remove non-Camino web passwords (we have no intention of doing so, but it's certainly possible), however I don't see how that would help the confusion about Safari's behavior. > Is there a way we can have an option for Camino to do the non-standard > thing and store its passwords differently? Someone could write an input manager hack that would have that effect, or you could use a third-party password management solution. We aren't going to write and maintain a second, non-standard password storage system as part of Camino though, because that's not consistent with Camino's design philosophy or goals. > Being stuck on the right side of the argument but still being > hit by defective behavior is something that I think should be > dealt with in some way. I agree that Safari doesn't do a good job explaining the behavior, but again, whether or not the behavior itself is defective is a matter of opinion. Apple is clearly moving to a model where there is a central repository of certain types of data, and anyone can use or interact with that store. This is their model for passwords, for calendars, for todos, for rss subscriptions, for contacts, for cookies, etc. I understand your argument, but undermining a primary purpose of the OS's shared keychain system is not the right answer from our perspective, any more than it would be the right answer for Camino to stop using the keychain entirely if some application had a reset button that deleted *everything* in the keychain (which would be trivial to write). There are a lot of benefits for users to having data in shared, interoperable systems, and if every application stops using those systems as soon as any one application does something unexpected or undesirable, then the whole model collapses, and users are locked in to specific applications. The bottom line is that interoperability with the OS system of password storage (and by extension every application that also does the right thing) is an explicit feature of Camino, and not one that we are going to remove just because one client of that shared data (Safari) has a feature that is not sufficiently explained by that application. I understand that some people disagree with that position (heck, some people have asked us to stop using the keychain entirely, purely on the basis that they don't think we shouldn't share data with other applications); Camino's built-in password manager may not be the right password system for those people. -Stuart _______________________________________________ Camino mailing list Camino@mozdev.org https://www.mozdev.org/mailman/listinfo/camino
