The C++ source has access to the browser script source through
nsIBrowserDOMWindow. It is intended to be attached to the chrome DOMWindow
of a toplevel browser window (a XUL window). A DOMWindow that does not
happen to be a browser chrome window will simply have no access to any such
interface.
Load a URI
| aURI | the URI to open. null is allowed. If null is passed in, no load will be done, though the window the load would have happened in will be returned. |
| aWhere | see possible values described above. |
| aOpener | window requesting the open (can be null). |
| aContext | the context in which the URI is being opened. This is used only when aWhere == OPEN_DEFAULTWINDOW. |
| the window into which the URI was opened. |
As above, but return the nsIFrameLoaderOwner for the new window.
// XXXbz is this the right API? Do we really need the opener here?
// See bug 537428
| aWindow | the window to test. |
| whether the window is the main content window for any currently open tab in this toplevel browser window. |
Values for openURI’s aWhere parameter.
Do whatever the default is based on application state, user preferences,
and the value of the aContext parameter to openURI.
Open in the “current window”. If aOpener is provided, this should be the
top window in aOpener’s window hierarchy, but exact behavior is
application-dependent. If aOpener is not provided, it’s up to the
application to decide what constitutes a “current window”.
Open in a new window.
Open in a new content tab in the toplevel browser window corresponding to
this nsIBrowserDOMWindow.
Open in an existing content tab based on the URI. If a match can’t be
found, revert to OPEN_NEWTAB behavior.
Values for openURI’s aContext parameter. These affect the behavior of
OPEN_DEFAULTWINDOW.
external link (load request from another application, xremote, etc).
internal open new window