MDN wants to talk to developers like you:

Trabajar con ventanas desde código chrome

Imagen:traduccion-pendiente.png Esta página está traduciéndose a partir del artículo Working_with windows in chrome code, razón por la cual puede haber algunos errores sintácticos o partes sin traducir. Puedes colaborar continuando con la traducción

Este artículo describe el trabajo con múltiples ventanas en código chrome Mozilla (aplicaciones XUL y extensiones). Contiene trucos y código de ejemplo para abrir nuevas ventanas, encontrar las ventanas ya abiertas, y pasar datos entre diferentes ventanas.

Abrir ventanas

Para abrir una ventana nueva, solemos usar la llamada DOM o window.openDialog, así:

var win ="chrome://myextension/content/about.xul", 
                      "aboutMyExtension", "chrome,centerscreen"); 

El primer parámetro de es la URI del archivo XUL que describe la ventana y su contenido.

El segundo parámetro es el nombre de la ventana. El nombre de la ventana puede ser usado en enlaces o formularios como el atributo target. Esto es diferente del título de ventana visible por el usuario, que es especificado usando XUL.

El tercer, y opcional, parámetro es una lista de las características especiales que la ventana debería tener.

La función window.openDialog funciona de forma similar, pero te permite especificar argumentos opcionales que pueden ser referenciados desde el código JavaScript. También maneja las funciones de ventana de forma un poco distinta, suponiendo siempre que la funcionalidad dialog es especificada.

Si el objeto Window no está disponible (por ejemplo, al abrir una ventana desde código de componente XPCOM), puedes querer usar la interfaz nsiWindowWatcher. Sus parámetros son similares a En realidad, la implementación de llama a métodos de nsiWindowWatcher.

var ww = Components.classes[";1"]
var win = ww.openWindow(null, "chrome://myextension/content/about.xul",
                        "aboutMyExtension", "chrome,centerscreen", null);

Window object

Note the win variable in the above section, which is assigned the return value of It can be used to access the opened window. The return value of (and similar methods) is a Window object (usually ChromeWindow), of the same type that the window variable.

Technically speaking, it implements a number of interfaces, including nsIDOMJSWindow and nsIDOMWindowInternal, but it also contains the user-defined properties for global variables and functions of the window. So, for example, to access the DOM document corresponding to the window, you can use win.document.

Note however, that the open() call returns before the window is fully loaded, so some calls, like win.document.getElementById() will fail. To overcome this difficulty, you can move the initialization code to a load handler of the window being opened or pass a callback function, as described below.

You can get a Window object from a document using document.defaultView.

Content windows

When a XUL window contains a widget capable of displaying a page, such as <browser> or <iframe>, the document in that widget is, naturally, separate from the document of the chrome window itself. There also is a Window object for each sub-document, although there's no window in a common sense for the sub-document.

The same holds for chrome windows opened inside a tab of <tabbrowser>. The elements above the chrome document opened in the tab are separate from your chrome document.

The following two subsections describe how to cross chrome-content boundaries in either way, i.e. accessing elements which are ancestors of your chrome document, or accessing elements which are descendants of your chrome document (but nevertheless in a different context).

Accessing content documents

Assume you have a document loaded in a <tabbrowser>, <browser>, or <iframe> element inside your document. You can use browser.contentDocument to access that document and browser.contentWindow to the Window object of that document.

You should be aware of XPCNativeWrappers when working with untrusted content. With XPCNativeWrappers turned on (which is the default in Firefox 1.5+), your extension can safely access the DOM of the content document, but not the content JavaScript. Bypassing XPCNativeWrapper to work with content JavaScript directly can lead to security problems.

See Interaction between privileged and non-privileged pages if you need to interact with the content page.

The content shortcut

In case of <browser type="content-primary"/>, you can use the content shortcut property to accesss the Window object of the content document. For example:

// alerts the title of the document displayed in the content-primary widget


For example, you can use content.document in a browser.xul overlay to access the web page in the selected tab in a Firefox window.

Some examples use _content instead of content. The former has been deprecated for a while, and you should use content in the new code.

Accessing a document in the sidebar

Firefox has a sidebar, which is implemented as a <browser> element with id="sidebar". To access the elements and variables inside the sidebar, you need to use document.getElementById("sidebar").contentDocument or .contentWindow, like when Accessing content documents.

For more sidebar tips, see Code snippets:Sidebar.

Accessing the elements of the top-level document from a child window

The opposite case is when you want to access the chrome document from a privileged script loaded in a <browser> or an <iframe>.

A typical case when this can be useful is when your code runs in the sidebar in the main Firefox window and you want to access the elements in the main browser window.

The DOM tree, as shown by the DOM Inspector, can look like this:

  window                 main-window
          window         myExtensionWindow

where the child window is where your code runs in.

Your task is to access elements above your chrome document, i.e. to break out of your chrome window and access the ancestors. This can be done using the following statement:

var mainWindow = window.QueryInterface(Components.interfaces.nsIInterfaceRequestor)

This allows you to cross the chrome-content boundaries, and returns the main window object.

Finding already opened windows

The window mediator XPCOM component (nsIWindowMediator interface) provides information about existing windows. Two of its methods are often used to obtain information about currently open windows: getMostRecentWindow and getEnumerator. Please refer to the nsIWindowMediator page for more information and examples of using nsIWindowMediator. === Example: Opening a window only if it's not opened already === XXX TBD

Passing data between windows

When working with multiple windows, you often need to pass information from one window to another. Since different windows have separate DOM documents and global objects for scripts, you can't just use one global JavaScript variable in scripts from different windows.

There are several techniques of varying power and simplicity that can be used to share data. We'll demonstrate them from the simplest to the most complex in the next few sections.

Example 1: Passing data to window when opening it with openDialog

When you open a window using window.openDialog or nsIWindowWatcher.openWindow, you can pass an arbitrary number of arguments to that window. Arguments are simple JavaScript objects, accessible through window.arguments property in the opened window.

In this example, we're using window.openDialog to open a progress dialog. We pass in the current status text as well as the maximum and current progress values. Note that using nsIWindowWatcher.openWindow is a bit less trivial . TODO: link to How To Pass an XPCOM Object to a New Window when it has a more useful example

Opener code:

                  "myProgress", "chrome,centerscreen", 
                  {status: "Reading remote data", maxProgress: 50, progress: 10} );


<?xml version="1.0"?>
<?xml-stylesheet href="chrome://global/skin/" type="text/css"?>

<window onload="onLoad();" xmlns="">
  var gStatus, gProgressMeter;
  var maxProgress = 100;
  function onLoad() {
    gStatus = document.getElementById("status");
    gProgressMeter = document.getElementById("progressmeter");
    if("arguments" in window && window.arguments.length > 0) {
      maxProgress = window.arguments[0].maxProgress;

  function setProgress(value) {
    gProgressMeter.value = 100 * value / maxProgress;

  function setStatus(text) {
    gStatus.value = "Status: " + text + "...";
<label id="status" value="(No status)"/>
  <progressmeter id="progressmeter" mode="determined"/>
  <button label="Cancel" oncommand="close();"/>


Example 2: Interacting with the opener

Sometimes an opened window needs to interact with its opener; for example, it might do so in order to give notice that the user has made changes in the window. You can find the window's opener using its window.opener property or via a callback function passed to the window in a way described in the previous section.

Let's add code to the previous example to notify the opener when the user presses Cancel on the progress dialog.

  • Using window.opener. The opener property returns its window's opener; that is, the Window object that opened it.

If we're sure the window that opened the progress dialog declares the cancelOperation function, we can use window.opener.cancelOperation() to notify it, like this:

<button label="Cancel" oncommand="opener.cancelOperation(); close();"/>
  • Using a callback function. Alternatively, the opener window can pass a callback function to the progress dialog in the same way we passed the status string in the previous example:
function onCancel() {
  alert("Operation canceled!");


                  "myProgress", "chrome,centerscreen", 
                  {status: "Reading remote data", maxProgress: 50, progress: 10},

The progress dialog can then run the callback like this:

<button label="Cancel" oncommand="window.arguments[1](); close();"/>

Example 3: Using nsIWindowMediator when opener is not enough

The window.opener property is very easy to use, but it's only useful when you're sure that your window was opened from one of a few well-known places. In more complicated cases you need to use the nsIWindowMediator interface, introduced above.

One case in which you might want to use nsIWindowMediator is in an extension's Options window. Suppose you're developing a browser extension that consists of a browser.xul overlay and an Options window. Suppose the overlay contains a button to open the extension's Options window which needs to read some data from the browser window. As you may remember, Firefox's Extension Manager can also be used to open your Options dialog.

This means the value of window.opener in your Options dialog is not necessarily the browser window -- instead, it might be the Extension Manager window. You could check the location property of the opener and use opener.opener in case it's the Extension Manager window, but a better way is to use nsIWindowMediator:

var wm = Components.classes[";1"]
var browserWindow = wm.getMostRecentWindow("navigator:browser");
// read values from |browserWindow|

You might be tempted to use a similar technique to apply the changes the user made in the Options dialog, but a better way to do that is to use preferences observers.

Advanced data sharing

The above code is useful when you need to pass data from one window to another or to a set of windows, but sometimes you just want to share a JavaScript variable in common between different windows. You could declare a local variable in each window along with corresponding setter functions to keep the "instances" of the variable in sync across windows, but fortunately, there's a better way.

To declare a shared variable, we need to find a place that exists while the application is running and is easily accessible from the code in different chrome windows. There are actually a few such places.

Using JavaScript code modules

JavaScript code modules is a simple method for creating shared global singleton objects that can be imported into any other JavaScript scope. The importing scope will have access to the objects and data in the code module. Since the code module is cached, all scopes get the same instance of the code module and can share the data in the module. See Components.utils.import for more information.

  • Pros:
    • It's the "right way"
    • Very simple to make and import.
    • No need to build an XPCOM component.
  • Cons:
    • Only works in Firefox 3 or newer.
    • The scope is shared between modules and the importing scope, so you have to worry about name collisions.
    • You can't use the window object, its members, like alert and open, and many other objects available from inside a window. The functionality isn't lost, however -- you just have to use the XPCOM components directly instead of using convenient shortcuts. Of course, this doesn't matter if you just store data in the component.

Using an XPCOM singleton component

The cleanest and most powerful way to share data is to define your own XPCOM component (you can write one in JavaScript) and access it from anywhere using a getService call:

  • Pros:
    • It's the "right way".
    • You can store arbitrary JavaScript objects in the component.
    • The scope is not shared between components, so you don't have to worry about name collisions.
    • Works in older versions of Firefox.
  • Cons:
    • You can't use the window object, its members, like alert and open, and many other objects available from inside a window. The functionality isn't lost, however -- you just have to use the XPCOM components directly instead of using convenient shortcuts. Of course, this doesn't matter if you just store data in the component.
    • Learning to create XPCOM components takes time.

There are several articles and books about creating XPCOM components online.

Using FUEL Application object

The FUEL JavaScript library has a simple method for sharing data between windows. The Application object supports a storage property which can be used to store data globally. This method is a simplified form of the XPCOM singleton method., data);

var data =, default);

where: keyname is a string used to identify the data
       data is the data
       default is the data value to return if keyname does not exists
  • Pros:
    • Its the "right way".
    • You can store arbitrary JavaScript objects in the component.
    • The scope is not shared between components, so you don't have to worry about name collisions.
    • No need to build an XPCOM component.
  • Cons:
    • Only works in Firefox 3 or newer.
    • You can't use the window object, its members, like alert and open, and many other objects available from inside a window. The functionality isn't lost, however -- you just have to use the XPCOM components directly instead of using convenient shortcuts. Of course, this doesn't matter if you just store data in the component.

Storing shared data in preferences

If you just need to store a string or a number, writing a whole XPCOM component may be an unnecessary complication. You can use the preferences service in such cases.

  • Pros:
    • Quite easy to use for storing simple data.
  • Cons:
    • Can't easily be used to store complex data.
    • Abusing the preferences service and not cleaning up after yourself can cause prefs.js to grow large and slow down application startup.

See Code snippets:Preferences for detailed description of the preferences system and example code.


var prefs = Components.classes[";1"]
var branch = prefs.getBranch("extensions.myext.");
var var1 = branch.getBoolPref("var1"); // get a pref

The hidden window hack

Some extension authors use the special hidden window to store their data and code. The hidden window is similar to a regular window, but unlike any other window, it's available the whole time the application is running, and isn't visible to user. The document loaded into this window is chrome://browser/content/hiddenWindow.xul on Macs where it is used to implement the menus and resource://gre/res/hiddenWindow.html on other operating systems. Eventually this window will be removed for operating systems where it isn't needed (bug 71895).

A reference to the hidden window can be obtained from the nsIAppShellService interface. As any other DOM object it allows you to set custom properties:

var hiddenWindow = Components.classes[";1"]
hiddenWindow.myExtensionStatus = "ready";

However, objects put into the hidden window will still belong to the window that created them. If a method of such an object accesses properties of the window object like XMLHttpRequest you might be confronted with an error message because the original window has been closed. To avoid this you can load the objects with a script file into the hidden window:

var hiddenWindow = Components.classes[";1"]

With globalObject.js containing something like:

var myExtensionObject = {
  doSomething: function() {
    return new XMLHttpRequest();
  • Pros:
    • If you are running code in the hidden window, the window object and its properties are available, unlike the component case.
    • You can store arbitrary JavaScript objects in the hidden window.
  • Cons:
    • It's a hack.
    • The same window is accessed by different extensions, you have to use long variable names to avoid conflicts.
    • The hidden window may be removed from Windows/Linux builds.

See also

Etiquetas y colaboradores del documento

 Colaboradores en esta página: another_sam, fscholz, Mgjbot
 Última actualización por: another_sam,