Closed Bug 382180 Opened 17 years ago Closed 17 years ago

HTTP auth dialogs don't come up if login manager croaks

Categories

(Toolkit :: Password Manager, defect)

defect
Not set
minor

Tracking

()

RESOLVED FIXED
mozilla1.9beta1

People

(Reporter: Dolske, Assigned: Dolske)

References

Details

(Whiteboard: [has patch, review])

Attachments

(1 file, 3 obsolete files)

Spinoff from bug 380961... storage-Legacy.js was throwing because it didn't like an item in signons2.txt. While a failure in the login manager is obviously likely to not fill in an existing password, the code should ideally be fail-safe enough so that you at least get an authentication prompt you can fill out manually.
Flags: blocking-firefox3?
Flags: blocking-firefox3? → blocking-firefox3+
Target Milestone: --- → Firefox 3 alpha6
Assignee: nobody → dolske
moving out, needs to make b1...
Target Milestone: Firefox 3 alpha6 → Firefox 3 beta1
Target Milestone: Firefox 3 M7 → Firefox 3 M8
Target Milestone: Firefox 3 M8 → Firefox 3 M9
Attached patch Patch for review, v.1 (obsolete) (deleted) — Splinter Review
This basically wraps up the promptAuth() code in try/catch blocks. I used dump() to report an error instead of this.log() juuuuust in case it's the logging causing a problem. Maybe that's too paranoid? I'll also attach a version of this patch that ignores whitespace, since the indenting from the |try {}| wrappers isn't really changing code.
Attachment #284360 - Flags: review?(gavin.sharp)
Attached patch Whitespace ignored, v.1 (obsolete) (deleted) — Splinter Review
Whiteboard: [need review gavin]
Whiteboard: [need review gavin] → [has patch][need review gavin]
Target Milestone: Firefox 3 M9 → Firefox 3 M10
Comment on attachment 284360 [details] [diff] [review] Patch for review, v.1 I'm a bit nervous about adding try/catch blocks around large amounts of code because similar approaches to robustness have caused hard-to-find and hard-to-debug-remotely problems in the past, but I suppose this is OK as long as the failure cases aren't something we'd miss in testing, which appears to be the case here, and the error reporting for any exceptions is solid. I think you should use Components.utils.reportError() instead or in addition to the dump()s in the catch() blocks, though. r=me with that.
Attachment #284360 - Flags: review?(gavin.sharp) → review+
Whiteboard: [has patch][need review gavin] → [has patch]
Whiteboard: [has patch] → [has patch, review]
Attachment #284360 - Flags: approval1.9?
Attached patch Patch w/nit fixed, v.2 (obsolete) (deleted) — Splinter Review
Attachment #284360 - Attachment is obsolete: true
Attachment #284361 - Attachment is obsolete: true
Attachment #285638 - Flags: approval1.9?
Attachment #284360 - Flags: approval1.9?
Attached patch Patch w/nit fixed, v.3 (deleted) — Splinter Review
Oops, left a file out from v.2.
Attachment #285638 - Attachment is obsolete: true
Attachment #285639 - Flags: approval1.9?
Attachment #285638 - Flags: approval1.9?
Attachment #285639 - Flags: approvalM9+
Attachment #285639 - Flags: approval1.9?
Attachment #285639 - Flags: approval1.9+
Checking in toolkit/components/passwordmgr/src/nsLoginManagerPrompter.js; /cvsroot/mozilla/toolkit/components/passwordmgr/src/nsLoginManagerPrompter.js,v <-- nsLoginManagerPrompter.js new revision: 1.12; previous revision: 1.11 done Checking in embedding/components/windowwatcher/src/nsPrompt.cpp; /cvsroot/mozilla/embedding/components/windowwatcher/src/nsPrompt.cpp,v <-- nsPrompt.cpp new revision: 1.32; previous revision: 1.31
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Target Milestone: Firefox 3 M10 → Firefox 3 M9
This appears to have broken embedders using nsIAuthPrompt; see bug 403115 for details.
Blocks: 403115
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: