Consumer that asked for fixed up URI.
The fixed-up original input, never using a keyword search. (might be null if the original input was not recoverable as a URL, e.g. "foo bar"!)
Whether we changed the protocol instead of using one from the input as-is.
Whether we created an alternative URI. We might have added a prefix and/or suffix, the contents of which are controlled by the browser.fixup.alternate.prefix and .suffix prefs, with the defaults being "www." and ".com", respectively.
The keyword as used for the search (post trimming etc.) empty string if no keyword search was done.
The name of the keyword search provider used to provide a keyword search; empty string if no keyword search was done.
The original input
The POST data to submit with the returned URI (see nsISearchSubmission).
Our best guess as to what URI the consumer will want. Might be null if we couldn't salvage anything (for instance, because the input was invalid as a URI and FIXUP_FLAG_ALLOW_KEYWORD_LOOKUP was not passed)
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.
Generated using TypeDoc
Interface indicating what we found/corrected when fixing up a URI