From 853c7fc3d91ee27d8fbc38047b0b5db2b2e87f0e Mon Sep 17 00:00:00 2001 From: "mscott%netscape.com" Date: Fri, 5 Nov 1999 23:26:16 +0000 Subject: [PATCH] (not part of the build) GetProtcocolHandler needs to pass in the uri we are trying to open so the listener can pick an appropriate p.h. based on the protocol of the uri. (if they so choose). --- uriloader/base/nsIURIContentListener.idl | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/uriloader/base/nsIURIContentListener.idl b/uriloader/base/nsIURIContentListener.idl index f723474b1118..acd87e7e82d3 100644 --- a/uriloader/base/nsIURIContentListener.idl +++ b/uriloader/base/nsIURIContentListener.idl @@ -27,6 +27,7 @@ interface nsIProtocolHandler; interface nsIStreamListener; interface nsIChannel; +interface nsIURI; [scriptable, uuid(94928AB3-8B63-11d3-989D-001083010E9B)] interface nsIURIContentListener : nsISupports @@ -35,8 +36,13 @@ interface nsIURIContentListener : nsISupports a specific content handler. Content listener's do not need to support this method if they want the uri dispatcher to find the default protocol handler from the registry. + + aURI --> the uri we need a protocol handler for + aProtocolHandler --> the protocol handler you want the uri loader + to use. You can pass back null if you want the uri loader to look + up an appropriate protocol handler */ - readonly attribute nsIProtocolHandler protocolHandler; + void getProtocolHandler(in nsIURI aURI, out nsIProtocolHandler aProtocolHandler); /* The URIDispatcher will give the content listener a shot at handling the content before it tries other means. If the content listener