MDN wants to learn about developers like you: https://qsurvey.mozilla.com/s3/MDN-dev-survey

Add-ons using the techniques described in this document are considered a legacy technology in Firefox. Don't use these techniques to develop new add-ons. Use WebExtensions instead. If you maintain an add-on which uses the techniques described here, consider migrating it to use WebExtensions.

Starting from Firefox 53, no new legacy add-ons will be accepted on addons.mozilla.org (AMO) for desktop Firefox and Firefox for Android.

Starting from Firefox 57, only extensions developed using WebExtensions APIs will be supported on Desktop Firefox and Firefox for Android.

Even before Firefox 57, changes coming up in the Firefox platform will break many legacy extensions. These changes include multiprocess Firefox (e10s), sandboxing, and multiple content processes. Legacy extensions that are affected by these changes should migrate to use WebExtensions APIs if they can. See the "Compatibility Milestones" document for more information.

A wiki page containing resources, migration paths, office hours, and more, is available to help developers transition to the new technologies.

The BrowserApp object is only available to privileged code running on Firefox for Android, and is intended for use by Firefox for Android add-ons.

Summary

BrowserApp.getTabForBrowser() retrieves a tab, given the XUL browser object hosted by that tab.

Syntax

var tab = window.getTabForBrowser(browser);

browser
The browser object hosted by this tab, which can be found as the browser property of the Tab object.

Returns

tab: the Tab corresponding to this browser.

Example

This function returns the ID of a tab, given the tab's browser:

function tabID(browser) {
  let tab = window.BrowserApp.getTabForBrowser(browser);
  return tab.id;
}

See Also

Document Tags and Contributors

 Contributors to this page: rebloor, andrewtruongmoz, wbamberg
 Last updated by: rebloor,