loadOneTab inBackground

The place to report Pale Moon specific bugs on the Windows operating system.

Moderator: satrow

User avatar
RealityRipple
Apollo supporter
Apollo supporter
Posts: 46
Joined: 2018-05-17, 02:34
Contact:

loadOneTab inBackground

Unread post by RealityRipple » 2019-07-07, 21:26

Is the inBackground parameter of the gBrowser.loadOneTab function still supposed to be respected? I'm testing an extension of mine that makes use of the parameter in Pale Moon and Basilisk, and with the "When I open a link in a new tab, switch to it immediately" preference enabled, the tab that's supposed to be loaded in the background is instead loaded in the foreground, resulting in all kinds of unwanted behavior and non-functionality. Does it rely on any other parameters or methods of being called to function correctly? I've tried both the single array parameter and independent parameters with the same result.

vannilla
Astronaut
Astronaut
Posts: 629
Joined: 2018-05-05, 13:29

Re: loadOneTab inBackground

Unread post by vannilla » 2019-07-07, 21:39

I think what happens is that the tab is loaded into the background, but since the browser is set to switch to new tabs immediately, it appears like it's opened in the foreground.

User avatar
JustOff
Localization Coordinator
Localization Coordinator
Posts: 1780
Joined: 2015-09-03, 19:47
Location: UA
Contact:

Re: loadOneTab inBackground

Unread post by JustOff » 2019-07-07, 21:57

RealityRipple wrote:
2019-07-07, 21:26
Is the inBackground parameter of the gBrowser.loadOneTab function still supposed to be respected?
I use it in my extension and everything works as expected regardless of the "browser.tabs.loadInBackground" setting.
Here are the add-ons I made in a spare time. That was fun!

User avatar
RealityRipple
Apollo supporter
Apollo supporter
Posts: 46
Joined: 2018-05-17, 02:34
Contact:

Re: loadOneTab inBackground

Unread post by RealityRipple » 2019-07-08, 01:32

JustOff wrote:
2019-07-07, 21:57
RealityRipple wrote:
2019-07-07, 21:26
Is the inBackground parameter of the gBrowser.loadOneTab function still supposed to be respected?
I use it in my extension and everything works as expected regardless of the "browser.tabs.loadInBackground" setting.
Does your extension try to grab the selected text of the current tab immediately after trying to load a new tab in the background?

Post Reply