Ability to create unloaded tabs by chrome.tabs.create
As question says:
Ability to create discarded tabs (unloaded). Tabs should find favicon from cached url if available. If not, use just default favicon. Also there should be a parameter for titles, an array with titles should match the url length.
In case of windows.create, first tab should be loaded, as usual. chrome.windows.create({url: [], title: [], discarded: true}, function(window) {}); chrome.tabs.create({url: "your url here", title: "your title here", discarded: true}, function(tab) {});
Все ответы (6)
Would you care to rephrase your question as no idea what you are asking for. Thanks.
As I have no idea where to post feature requests, I posted it here. Question is directed to Firefox developers. My suggestion is to extend WebExtensions API to add ability to create tabs with unloaded (discarded) state. Preload only favicon and title.
What about this:
browser.tabs.create({ url: 'https://mozilla.org', active: false})
.then(tab => browser.tabs.discard(tab.Id))
The good place to meet WebExt devs is here: https://discourse.mozilla.org/c/add-ons/development
TyDraniu said
What about this: browser.tabs.create({ url: 'https://mozilla.org', active: false}) .then(tab => browser.tabs.discard(tab.Id)) The good place to meet WebExt devs is here: https://discourse.mozilla.org/c/add-ons/development
I tried that method some time ago. It won't load favicon neither title until page is loaded. And for some reason tab is "dead". You can activate it but is just empty. I can delay or make loop and wait until tab is loaded and discard it afterwards.
My point, was to not load anything in the first place to save internet traffic, memory and cpu, providing title and/or faviconUrl.
And by the way, you have error there "tab.Id" should be "tab.id"
I will take a look at the provided link.
Изменено kroppy
I don't think FF forum can help with programming a userChrome.css option that is beyond the scope of the normal FF end user help forum. If you got that from someone else then you should contact them for support on the css side if you created it yourself then you will have to do the debugging and testing on how it works.
WestEnd said
I don't think FF forum can help with programming a userChrome.css option that is beyond the scope of the normal FF end user help forum. If you got that from someone else then you should contact them for support on the css side if you created it yourself then you will have to do the debugging and testing on how it works.
I think your answer refers to someone else. Wrong tab maybe?