Please note, this is a STATIC archive of website from 03 Nov 2016, does not collect or store any user information, there is no "phishing" involved.

This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.

This feature is obsolete. Although it may still work in some browsers, its use is discouraged since it could be removed at any time. Try to avoid using it.

This function was only available in the original, XUL-based version of Firefox for Android, which is no longer supported; for that reason, this function is obsolete and should never be used.


Because opening windows on mobile isn't necessarily appropriate, the Firefox Mobile team designed the importDialog() method to replace window.openDialog(). Instead of opening a new window, it merges the specified XUL dialog into the main window.


newDialog = importDialog(aParent, aSrc, aArguments) 
The opened window
The dialog's parent; can be null.
The chrome URL of the XUL dialog.
A JavaScript object containing data to pass to the dialog.


var dialog = importDialog(null, "chrome://myextension/content/dialog.xul", myObject);


The XUL passed to importDialog() is very similar to XUL passed to window.openDialog(), with some limitations and caveats:

  • Only <dialog> top level elements are permitted.
  • Scripts are loaded via an attribute on the <dialog> element, not via the <script> tag.

The XUL is merged into the existing window, almost like a XUL overlay. Because of this, element ID and JavaScript conflicts are possible, just like overlays. So be careful.


This is not part of any specification.

Document Tags and Contributors

 Contributors to this page: Ac1521, Sheppy, fscholz, MHasan, teoli, kscarfone, damien.flament, Sonnyp
 Last updated by: Ac1521,