I don't see why the current iface has to be a constraint, I was just thinking of a quicky and dirty way to do it.

Jud

Adam Lock wrote:
[EMAIL PROTECTED]">Judson Valeski wrote:

We currently don't have this layer. We *could* bake the nsresult into the param list of the nsIPromptService, and rename it to nsIPromptService2 or something, but, that injects context in what is otherwise a generic UI iface.

If the current form of the interface is a constraint, perhaps something could be done with the DOM window parameter that is passed in to each method? The prompt service can go looking for the context if it wants it by GI/QI'ing the DOM for additional information that could be stuck on some kind of nsIErrorInfo interface.




Reply via email to