James Newell wrote:
Throwing the error from the newChannel function works, however it comes
up as a message box regardless of the setting
pref("browser.xul.error_pages.enabled", true); whilst other protocols
adhere to this setting.
Yeah. Like biesi said, newChannel errors can't use error pages at the moment,
so they get an error dialog. You'd have to throw this from asyncOpen, I think,
to get an error page. Or pass it to onStopRequest. Either one would work, but
asyncOpen is probably easier.
-Boris
_______________________________________________
dev-tech-xpcom mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-xpcom
