We need to supply error codes (nsresults) to nsIPrompt implementations so they can interrigate the error condition without having to parse the error message string. Current callers of nsIPrompt interfaces will simply float the error that caused them to use nsIPrompt, into the new methods.
1. DNS failure (webshell,,) 2. Connection refused (webshell,,) 3. Connection timeout (webshell,,) 4. secure page transition (psm,,) 5. repost data (docshell,,) 6. cookies (cookie module, universal dialog,) 7. wallet (wallet module, universal dialog,) 8. JS eval (caps module, universal dialog,) 9. unknown protocol (docshell,,) 10. FTP/HTTP username and password gathering for auth (FTP and HTTP modules, user/password,) 11. DOM. The DOM provides access to a prompter via it's GetPrompter() method (.prompter in JS, alert/confirm) 12. XML parser throws an error when it confronts a poorly formed XML doc. 13. Unknown content type dialog
Watch out for bug 46859 which we hope to land today or tomorrow. (BTW, I'm not sure what your 13 items mean.)
I'll grab this one.
Assignee: dougt → valeski
marking as invalid. nsIPrompt is for UI throwing *only*, an error conditions are/shoudl be reflected in nsIWebProgress|Listener.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID
Updating QA Contact
QA Contact: jrgm → mdunn
verifying as invalid. nsIPrompt is for UI throwing *only*, an error conditions are/shoudl be reflected in nsIWebProgress|Listener.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.