Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

When browser.tabs.loadBookmarksInTabs=truedoesn't use existing blank "New" Tab

  • 7 përgjigje
  • 3 e kanë hasur këtë problem
  • 22 parje
  • Përgjigjja më e re nga the-edmeister

more options

Using FF Quantum (57.0.2 64-bit,) when I have the config option to load bookmarks in a new tab set to true, and I then open a bookmark, FF doesn't use the existing blank New Tab. So I still have a blank New Tab in addition the the tab opened for the bookmark.

Not such a big deal, but when I then try to close FF, instead of just closing the window, it tells me I have TWO tabs open, and it asks if I really want to close. This is annoying.

Either closing should ignore blank tabs, or opening bookmarks should re-use blank tabs.

Using FF Quantum (57.0.2 64-bit,) when I have the config option to load bookmarks in a new tab set to true, and I then open a bookmark, FF doesn't use the existing blank New Tab. So I still have a blank New Tab in addition the the tab opened for the bookmark. Not such a big deal, but when I then try to close FF, instead of just closing the window, it tells me I have TWO tabs open, and it asks if I really want to close. This is annoying. Either closing should ignore blank tabs, or opening bookmarks should re-use blank tabs.

Krejt Përgjigjet (7)

more options

You did this in about : config. Reverse your changes and will longer say have 2 open. About:config has changed and so is what you can do in there.

Reverse it or looking a reinstall.

more options

WoofGrrrr said

Either closing should ignore blank tabs, or opening bookmarks should re-use blank tabs.

A New Tab isn't blank it is about:newtab, an internal "page".

And that browser.tabs.loadBookmarksInTabs pref is designed to open a new tab which has the bookmarked page and not use an existing tab.

more options

I think the same happens when the current page is about:blank, so there is always a new tab opened regardless of the content of the current tab.

more options

cor-el said

I think the same happens when the current page is about:blank, so there is always a new tab opened regardless of the content of the current tab.

That's the problem. I wind up with a blank tab. When I then try to close the app, it counts that blank tab. And since there is now more than one tab open, I get the dialog asking if I really want to close the app. Unless, of course, I have MANUALLY deleted the blank tab.

more options

You can set this pref to false on the about:config page to avoid closing Firefox when you close the last open tab.

  • browser.tabs.closeWindowWithLastTab = false
more options

cor-el said

You can set this pref to false on the about:config page to avoid closing Firefox when you close the last open tab.
  • browser.tabs.closeWindowWithLastTab = false

I think maybe you missed my point??? I'm not talking about NOT closing the window when the LAST tab is closed. I *do* use that, but that's not the problem I have.

What I am saying is that I wind up with one or more blank tabs because opening "new" tabs doesn't use the existing, current blank tab.

The *REAL* gripe is, actually, that, because of this/these blank tab(s), when I go to close the window, I get the dialog saying I have more than one tab open, even when there is only ONE *non-blank* tab open. I have to stop and do something extra to close the browser window... for no reason.

I was suggesting that opening a new tab use the current, existing blank tab first. Perhaps give me an option to do that (like the "New Tab from Location Bar" extension's "Recycle current blank tab, instead of new tab" option.)

Or, give me an option, when clicking to close the window, to ignore blank tabs when deciding if more than one tab is open. Who cares if I accidentally close a blank tab?

Anyways, I thought I remembered Firefox before Quantum using existing blank tabs instead of opening a new tab, and if I am right about that, I would like Quantum to work the same way. I just don't remember having this problem before Quantum.

Ndryshuar nga WoofGrrrr

more options

WoofGrrrr said

Anyways, I thought I remembered Firefox before Quantum using existing blank tabs instead of opening a new tab, and if I am right about that, I would like Quantum to work the same way. I just don't remember having this problem before Quantum.

You may have had an extension in the past which modified that default action for browser.tabs.loadBookmarksInTabs opening a new tab with the bookmark. WebExtensions don't have the same capabilities that Legacy extensions had, which is why so many extensions have disappeared or have far fewer capabilities / features now. And in the long run will have far fewer support issues than in the past; much like what is being discussed in this thread.