Never means Never
Reported by
christop...@gmail.com,
May 20 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36 Steps to reproduce the problem: 1. Bank of Scotland website, Paypal, many many others 2. Log in 3. Chromium offers to save password 4. Click "NEVER" 5. Chromium offers to save the password next time, and again and again and again What is the expected behavior? Chromium does not offer to save the password after the "Never" button is clicked What went wrong? Its just... broken. Never means never. not offer every single time. Its bad security protocol. It interrupts the flow of the user's experience Did this work before? No Chrome version: 49.0.2623.87 Channel: stable OS Version: Version 49.0.2623.87 (64-bit) Flash Version: Shockwave Flash 21.0 r0
,
May 23 2016
,
May 23 2016
I think it's fixed in r387303. Should go live in version 52. Could you verify on Chrome Canary?
,
May 26 2016
Gentle Ping. @christopherreay: Could you please respond to the comment #3 Unable to repro this issue on Ubuntu Trusty (14.04) for Google Chrome Stable Version - 51.0.2704.63 Thank you.
,
Jun 8 2016
I too have this exceedingly tedious issue, and can confirm that it is *NOT* fixed in 51.0.2704.63. I have tried removing and re-adding from the "Never..." list, clearing my cache and cookies, and trying a new user profile. No dice. UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.63 Safari/537.36
,
Jun 9 2016
What is the site for reproduction?
,
Jun 10 2016
Now that I look around, it seems that some of the sites that it was happening on before aren't misbehaving anymore. Thank you for that. One that it still occurs on repeatedly is passpack.com, which I happen to use all the time. I'll report others if and as I run into them. Thanks
,
Jun 13 2016
passpack.com uses generated ids for username and password. It should be fixed in Chrome 52 that is on beta channel already. Could you verify?
,
Jun 13 2016
I pulled down the beta and confirmed, the bug is indeed fixed. Wonderful!
,
Jun 14 2016
Closing this issue as per the comment #9 Thank you. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by thestig@chromium.org
, May 20 2016