52295 - nsIPrompt methods need to include an error code as an "in" arg.

Status: VERIFIED INVALID

(Core Graveyard :: Embedding: APIs, defect, P1)

Description

[Judson Valeski]

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.

Comment 1

[Doug Turner (:dougt)]

    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 

Comment 2

[Warren Harris]

Watch out for bug 46859 which we hope to land today or tomorrow. (BTW, I'm not 
sure what your 13 items mean.)

Comment 3

[Judson Valeski]

I'll grab this one.

Comment 4

[Judson Valeski]

marking as invalid. nsIPrompt is for UI throwing *only*, an error conditions
are/shoudl be reflected in nsIWebProgress|Listener.

Comment 5

[Paul Wyskoczka]

Updating QA Contact

Comment 6

[Michael Dunn]

verifying as invalid.
nsIPrompt is for UI throwing *only*, an error conditions
are/shoudl be reflected in nsIWebProgress|Listener.