Optional aInstancePtr: objectA run time mechanism for interface discovery.
NS_OK if the interface is supported by the associated instance, NS_NOINTERFACE if it is not.
aInstancePtr must not be null.
[in] A requested interface IID
[out] A pointer to an interface pointer to receive the result.
Check whether a handler for a specific protocol exists. Specifically, this looks to see whether there are any known possible application handlers in either the nsIHandlerService datastore or registered with the OS.
true if we have a handler and false otherwise.
XXX shouldn't aProtocolScheme be an ACString like nsIURI::scheme?
The scheme from a url: http, ftp, mailto, etc.
Gets a human-readable description for the application responsible for handling a specific protocol.
NS_ERROR_NOT_IMPLEMENTED If getting descriptions for protocol helpers is not supported
NS_ERROR_NOT_AVAILABLE If no protocol helper exists for this scheme, or if it is not possible to get a description for it.
The scheme to look up. For example, "mms".
Retrieve the handler for the given protocol. If neither the application nor the OS knows about a handler for the protocol, the object this method returns will represent a default handler for unknown content.
the handler, if any; otherwise a default handler
the scheme from a URL: http, ftp, mailto, etc.
Note: aProtocolScheme should not include a trailing colon, which is part of the URI syntax, not part of the scheme itself (i.e. pass "mailto" not "mailto:").
Given a scheme, looks up the protocol info from the OS. This should be overridden by each OS's implementation.
An nsIHanderInfo for the protocol.
Was an OS default handler for this scheme found?
Check whether a handler for a specific protocol is "exposed" as a visible feature of the current application.
An exposed protocol handler is one that can be used in all contexts. A non-exposed protocol handler is one that can only be used internally by the application. For example, a non-exposed protocol would not be loaded by the application in response to a link click or a X-remote openURL command. Instead, it would be deferred to the system's external protocol handler. XXX shouldn't aProtocolScheme be an ACString like nsIURI::scheme?
Used to load a URI via an external application. Might prompt the user for permission to load the external application.
Embedders that do not expose the http protocol should not currently use web-based protocol handlers, as handoff won't work correctly (bug 394479).
The URI to load
The principal triggering this load.
The last post-redirect principal triggering this load. Used for display and permission purposes. If null, we'll use the triggering principal.
The context to parent the dialog against, and, if a web handler is chosen, it is loaded in this window as well. This parameter may be ultimately passed nsIURILoader.openURI in the case of a web handler, and aWindowContext is null or not present, web handlers will fail. We need to do better than that; bug 394483 filed in order to track.
If true, indicates the load was initiated by an external app.
Whether the document that triggered the load had user activation. Used for sandbox checks.
Set some sane defaults for a protocol handler object.
nsIHandlerInfo object, as returned by getProtocolHandlerInfoFromOS
was the object above created for an extant OS default handler? This is generally the value of the aFound out param from getProtocolHandlerInfoFromOS.
Generated using TypeDoc
The external protocol service is used for finding and launching web handlers (a la registerProtocolHandler in the HTML5 draft) or platform-specific applications for handling particular protocols.
You can ask the external protocol service if it has an external handler for a given protocol scheme. And you can ask it to load the url using the default handler.