Avatar for Username

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Realms (protected directory), FF 83.0, OSX 10.14.6

buggyisalreadytaken
buggyisalreadytaken
more options

Since the update, I'm unable to access ANY protected directories on any sites (those where a small modal dialog box appears at the top of the page asking for a uid/pwd pair and displaying the name of the realm above that). The dialog box doesn't even appear, the page does not change from its previous location, and the "I'm thinking" animation in the tab continues forever without ever seeing an error message.

Any suggestions? Must I downgrade? (uck)

Since the update, I'm unable to access ANY protected directories on any sites (those where a small modal dialog box appears at the top of the page asking for a uid/pwd pair and displaying the name of the realm above that). The dialog box doesn't even appear, the page does not change from its previous location, and the "I'm thinking" animation in the tab continues forever without ever seeing an error message. Any suggestions? Must I downgrade? (uck)

Tutte le risposte (1)

buggyisalreadytaken
buggyisalreadytaken Utente che ha posto la domanda
more options

Here's what I believe happened, and someone less lazy than I may wish to file a bug report:

The 83.0 notes say that on OSX, minimized windows will no longer suck as much juice. In past versions, once you entered your master password, any minimized windows with a realm/password-challenge would maximize, and expect you to hit OK. In this instance, I had a minimized window with a URL in a realm, and on launch, it was not popping up to ask for my OK. Since this one realm had not been cleared, subsequent requests for other realms were waiting for the first credential challenge to be OKd, but I wasn't even aware this was waiting to happen. A solution would be to go back to the old behavior. Another would be to approve realms with the default values (hit "submit" for the user, basically), and only pull failures forward. Another would be to let these challenges be dealt with in parallel, rather than serially. A fourth solution would be to simply notify users of the need to deal with this manually.