I would like to get the URL of the current tab within a page action popup.
At first it seems obvious: Just use the tabs API. But that doesn't seem to be available on Android if I deciphering the docs correctly. So I kept looking for something else and found the onClicked event of the pageAction API.
The pageAction API seems to be listed as compatible with Android and the onClicked event is marked as supported. So that implies that it would actually return a tabs.Tab object. But does it really? Has anyone tried it?
What is the best way to retrieve the URL? I know I could just use a content script and let that run in every single tab and create a long lived messaging connection to send the URL to the page action popup whenever it is requested. But that would be very inefficient and make the code insanely complicated compared to how easy it would be using the tabs API.
Is there anything else I could do?
You can get it this way with webextensions. Take into account that if you want to debug a popup, you have to "prevent popups to be closed" (4-squares icon at the top-right of the browser's toolbox)
I hope this will help you,
Current (Firefox 54 and later)
As of Firefox 54, the
tabs
API is available in Firefox for Android. This means you can use the normal methods available to desktop Firefox. Specifically,chrome.tabs.query()
orbrowser.tabs.query()
. However, you will need theactiveTab
and/ortabs
permissions
in your manifest.json.chrome.tabs.query
:browser.tabs.query
:Prior to Firefox 54
If you have defined a page/browser action popup
If you have defined a popup for your page/browser action, then the
onClicked
event does not fire. Your popup is not passed any information when it is created/shown. Thus, you will not receive atabs.Tab
object. The normal way to obtain tab information is fromtabs.query
, which, as you have already determined, is not (yet) available in Firefox for Android.The APIs available to Firefox on Android are quite limited. For what you are wanting to do, using
webNavigation
events to keep a record of each tab's frame 0 URL would be more efficient than a content script in every page. You could use thewebNavigation.onCommitted
orwebNavigation.onCompleted
events depending on your needs. You will need to assume that the active tab of the current window is the one which most recently had awebNavigation
event, or perhaps you could also monitorwebRequest
events. However, any way that you do it, which tab you assume to be the current tab will just be an assumption, and will be inaccurate under some circumstances.A more accurate URL (and active tab determination) requires using a content script
If the page that is being visited changes the tab's URL through some method that does not trigger navigation, using
webNavigation
events will not give you the updated URL. As you have identified, without thetabs
API, the only way to be certain you have the actual current URL for the tab, when you define an actual page/browser action popup (and thus don't get atabs.Tab
object), is to inject a content script into every page. You will either need the content scripts to continuously update the URLs, or be listening withstorage.onChanged
for a request for that information from your background/popup script. Communication from the background/popup scripts to content scripts must be accomplished through thestorage
API due to not having thetabs
API (i.e. notabs.sendMessage
).Using page/browser action
onClicked
An alternative, which I have not tried on Firefox on Android, would be to not define an actual page/browser action popup. If you don't define an actual popup, you receive the
onClicked
event (getting thetabs.Tab
Object with both the active tab's ID and the URL) and then can open a pseudo-popup1.1. The implementation of opening a a pseudo-popup in my linked answer uses the
tabs
andwindows
APIs which are both currently unavailable for Firefox for Android. It could be re-written to use the above mentionedwebNavigation
listener to track tab URLs andwindow.open()
to open the window used for the pseudo-popup. Again, I have not tested this with Firefox on Android to determine that it actually works.