Bug 977037 has UX specs for tab-modal authentication prompts. Tab-modal auth prompts can already somewhat work, the patch in bug 1029744 can enable them. (There are problems if you trigger more than one at a time, though.) I _think_ it should be feasible to simply restyle the existing prompt to mostly-match the UX specs in 977037. The main catches would seem to be: - Getting the in-content prompt to overlap into chrome. Should be possible, but might be a pain with all the XBL/XUL involved. - Shares the existing <tabmodal> prompt implementation (good), but this one flavor of prompt will be styled radically different. I'd much rather have some complex CSS than a mostly-duplicate implementation of tab-modal prompts (which are already complex). Note that the current APIs basically only allow a single message string in the prompt -- hence the current blob of text like "A username and password are being requested by https://somesite.com. The site says: 'LDAP - Valid User Required'". We should fix that in a separate/followup bug, and will need to do so anyway for other reasons. [Brief explanation: The front-end code is invoked from Gecko via nsIAuthPrompt2's asyncPromptAuth(), but in turn actually uses nsIAuthPrompt's promptUsernameAndPassword() to display the UI. We'll need to have a fully async asyncPromptAuth() all the way through the frontend anyway. That API doesn't require the caller to pass in explicit strings, which makes it easier to show whatever UI it wants to.]