For my extension i sorely miss the bookmarks API, as well as the above mentioned tabs.query({}) API , since its mostly useless in the current (even nightly) version, as it only really returns the 1 or few last open tabs, instead of the hundreds i actually have opened.
@1gorlogius, can you share more about your workaround?
Prevents tabs which are opend in the background from loading until they have been manually activated once â Load Background Tabs on Select
I guess that behavior isnât needed on mobile. I believe tabs are automatically unloaded when the system is low on RAM. In fact, the apps themselves in Android are automatically unloaded in such cases. And when Firefox (or any Android browser) gets loaded again, only the front tab is loaded. But Iâm not 100% sure about it, feel free to correct me.
@denilsonsa, thatâs a good summary. Itâs also directly tied to the issues others have mentioned with tabs.query().
As I understand it, on Android tabs are unloaded much more aggressively than on desktop, so very few tabs in the UI layer (Fenix) have concrete tab instances behind them at the Gecko layer. Firefoxâs extensions system (part of Gecko) operates against these tab instances, which in turn explains why query() doesnât work as expected on Android.
1 Like
Did you open a bug report https://bugzilla.mozilla.org/ for this? If not, would you mind opening one? My gut feeling is that it would be best to have someone that works on GeckoView triage as it may be a symptom of a larger issue.