Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

"open all in tabs" doesn't work

  • 3 odgovora
  • 9 ima ovaj problem
  • 1 prikaz
  • Posljednji odgovor od the-edmeister

more options

I noticed that "Open all in tabs" for groups no longer works properly. I have a group set as my home page and that opens correctly. Now when I try to open all in tabs with another group, only the first tab loads correctly. The other tabs remain with the previously loaded pages.

I noticed that "Open all in tabs" for groups no longer works properly. I have a group set as my home page and that opens correctly. Now when I try to open all in tabs with another group, only the first tab loads correctly. The other tabs remain with the previously loaded pages.

Svi odgovori (3)

more options

Do you have that problem with the TabMix Plus extension disabled? A test to see if TMP is causing that fault.

If not a problem with it disabled, see the TMP forum about that issue. http://tmp.garyr.net/forum/

more options

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of your add-ons is causing your problem (switch to the DEFAULT theme: Tools > Add-ons > Themes). See Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems and Troubleshoot issues with plugins like Flash or Java to fix common Firefox problems

If it does work in Safe-mode then disable all your extensions and then try to find which is causing it by enabling one at a time until the problem reappears. You can use "Disable all add-ons" on the Safe mode start window to disable all extensions. You have to close and restart Firefox after each change via "File > Exit" (Mac: "Firefox > Quit"; Linux: "File > Quit")

more options

Thanks for the suggestions. I posted a follow-up to my original post last night that I came to suspect TMP myself and found that an update that hadn't yet been automatically installed fixed the problem. Don't know where the follow-up post landed.

At any rate, the problem is solved. Again, thanks for the help!