http://bugzilla.opensuse.org/show_bug.cgi?id=977941
http://bugzilla.opensuse.org/show_bug.cgi?id=977941#c7
--- Comment #7 from Nick Levinson ---
Maybe it was accidental the first time, but the repeated deletion of passwords
cannot reasonably be accidental, since I think if someone's telling us after
the fact that the passwords have been deleted and then repeating the news in
multiple weeks then someone would have told someone and people preparing the
updates would know that an update is going to delete passwords and they could
indeed tell users in advance. If they don't know which update is going to do it
then someone needs to look at the after-the-update announcements to see if
they're wrong and rewrite them or needs to trace through update patches to see
what's causing the password deletions. I'm not qualified to do that but someone
is.
I've started to take screenshots during software updates in order to catch more
specific details.
I don't know enough to call it specifically a Chromium regression. I'll leave
that to others to decide.
I have seen somewhere that an update can require a user's consent. I don't
remember whether it was in openSuse or Fedora Linux, but one update to a
Linux-platform app required the user to agree to license terms before the
update would be put into place. Since an update can require user approval of
license terms, it can do so for a warning about the effect of a change. If an
update is of several packages at once and posting a warning about just one is
not technically feasible, then send them as separate updates: one udate
requiring an advance agreement (to having seen the warning or to terms or to
anything else) with whatever that update includes and another update not
requiring any advance step.
--
You are receiving this mail because:
You are on the CC list for the bug.