You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resolution set to worksforme
Status changed from new to closed
We use multiple connections in browser for parallel background task executions. Please choose to save your password in the keychain to remove the need to display a login prompt.
==> This answer does not apply, the password was already saved in the keychain, and always has been. Clicking the checkbox "save in keychain" again has no effect at all.
For example, I click "refresh" in the browser, now within seconds, up to 6 or so "login failed" prompts get layered on top of each other, when I click "login" on them, each one usually spawns one more "login failed" dialog, so I have to click "login" again, before it finally disappears.
As stated in the previous ticket, this problem suddenly appeared something like 2 updates ago.
Please let me know if you are interested in a video capture of this behavior, and/or other info that might be related to this issue.
The text was updated successfully, but these errors were encountered:
Picking up from previous ticket #9885
Resolution set to worksforme
Status changed from new to closed
We use multiple connections in browser for parallel background task executions. Please choose to save your password in the keychain to remove the need to display a login prompt.
==> This answer does not apply, the password was already saved in the keychain, and always has been. Clicking the checkbox "save in keychain" again has no effect at all.
For example, I click "refresh" in the browser, now within seconds, up to 6 or so "login failed" prompts get layered on top of each other, when I click "login" on them, each one usually spawns one more "login failed" dialog, so I have to click "login" again, before it finally disappears.
As stated in the previous ticket, this problem suddenly appeared something like 2 updates ago.
Please let me know if you are interested in a video capture of this behavior, and/or other info that might be related to this issue.
The text was updated successfully, but these errors were encountered: