Bug 516747 part 2. Change nsIBrowserDOMWindow to allow some sort of setup where it works with frameloaders. r=bsmedberg

This commit is contained in:
Boris Zbarsky 2009-12-31 20:34:38 -05:00
Родитель 835cc0798e
Коммит 21cc323ae3
1 изменённых файлов: 10 добавлений и 1 удалений

Просмотреть файл

@ -39,8 +39,9 @@
interface nsIDOMWindow; interface nsIDOMWindow;
interface nsIURI; interface nsIURI;
interface nsIFrameLoaderOwner;
[scriptable, uuid(f9691a49-7fb3-4b54-bb11-a4f2e0b6eddb)] [scriptable, uuid(3ab89888-eb41-4dc8-b347-115555f47c80)]
/** /**
* The C++ source has access to the browser script source through * The C++ source has access to the browser script source through
@ -104,6 +105,14 @@ interface nsIBrowserDOMWindow : nsISupports
nsIDOMWindow openURI(in nsIURI aURI, in nsIDOMWindow aOpener, nsIDOMWindow openURI(in nsIURI aURI, in nsIDOMWindow aOpener,
in short aWhere, in short aContext); in short aWhere, in short aContext);
/**
* 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
*/
nsIFrameLoaderOwner openURIInFrame(in nsIURI aURI, in nsIDOMWindow aOpener,
in short aWhere, in short aContext);
/** /**
* @param aWindow the window to test. * @param aWindow the window to test.
* @return whether the window is the main content window for any * @return whether the window is the main content window for any