Comment 3 for bug 1982060

It is clearly a bug in Chrome. It is fetching three different resources
from the same server and not waiting for the user to respond to the
first password popup and using the password from there. Instead it is
popping up independent password dialogs for each resource.

I could of course workaround it by having the page load a single
password protected resource and wait for that load to finish before
proceeding but that just adds latency for everyone in order to avoid
password popups for one browser and then too only in the case of it
being freshly restarted.

Actually thinking about it maybe password protecting the root HTML will
do the trick with minimal performance impact on others.