Stored credentials auto-login creates unescapable history stack on Android+Twitter Mobile
Reported by
kanepy...@gmail.com,
Aug 10
|
|
Issue descriptionChrome Version : 68.0.3440.70 OS Version: A 7.1.1 URLs (if applicable) : https://twitter.com/CrimeADay/status/1027708885392678912 opened in a Chrome Custom Tab (NOT the Twitter app) Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari: Android Firefox: IE/Edge: Android What steps will reproduce the problem? 1. Have an old username/password pair in the credentials store that will not work to log in to Twitter 2. Open a tweet URL in Chrome 3. "Signing in with <username>" appears in a snack bar 4. Redirected to a "login failed" page 5. Press Back button 6. Steps 3-5 repeat forever What is the expected result? If automatic login fails, do not indefinitely repeat the process. After a few (3?) consecutive attempts to log in, set the "require user interaction" flag on the credentials. What happens instead of that? The history stack is inescapable and the tab must be closed with the upper left exit button. Please provide any additional information below. Attach a screenshot if possible. UserAgentString: Mozilla/5.0 (Linux; Android 7.1.1; Nexus 6 Build/N6F27M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.70 Mobile Safari/537.36 |
|
►
Sign in to add a comment |
|
Comment 1 by swarnasree.mukkala@chromium.org
, Aug 12