Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox 17.0 doesn't warn me when closing multiple tabs any more

  • 61 svar
  • 53 har dette problem
  • 5242 visninger
  • Seneste svar af cor-el

more options

hi all

Having updated to Firefox 17.0 (from 16.0.2), for some reason I don't get warned when closing multiple tabs any more.

I've confirmed the relevant options are selected and am 100% certain this was working fine before updating Firefox today.

I've replicated the problem on my vista 32bit platform and on XP 32 bit too.

I also looked at the changelog for Firefox 17 but can't see any explanation for this change in behaviour, although I wonder whether this might have something to do with it "772319 No option to disable the "Close other tabs" prompt."

As I use Tab Mix Plus (add-on), I've also checked Firefox in safemode and have found the native tab warnings not working, so have concluded it's an issue with Firefox (rather than something to do with an extension).

I've checked "about:config" and "browser.tabs.warnOnClose" is set to true, as is "browser.tabs.warnOnCloseOtherTabs".

Any help would be appreciated.


Thanks,

Gary

Ændret af gazzawazza den

Valgt løsning

weird it's finally working. so nvm i guess

Læs dette svar i sammenhæng 👍 0

Alle svar (20)

more options

??????????????????????

Ændret af NekoNekoMew den

more options

All of the follwing about:config settings are set to true: "extensions.tabmix.tabs.warnOnClose" "extensions.tabmix.protectedtabs.warnOnClose" "extensions.tabmix.warnOnclose" browser.tabs.warnOnCloseOtherTabs browser.tabs.warnOnClose

All normal settings under options are clicked it's FF17's fault

more options

@iamjayakumars:

Very helpful indeed, as it has been stated multiple times by gazzawazza (and me) that this setting does not have any effect in combination with Tab Mix Plus, which is the issue being discussed here.


@NekoNekoMew:

Please read more carefully what gazzawazza wrote repeatedly before, and what I already higlighted twice:

Just for your info, the about:config setting which gets locked is:

browser.warnOnQuit

As long as this setting is set to false, you won't get a warning.

more options

And like I've said multiple times IK about TMP error but in my case mine is set to true and is not locked which is why I'm confused as to why I'm not getting any warnings. Isn't reading fun :3?

Ændret af NekoNekoMew den

more options

Post a screenshot of browser.warnOnQuit set to true while TMP is active.

"Isn't reading fun :3?"

Yes ... if you can.

more options

You were saying?

more options

Anywho, like i was saying reading is fun :3

more options

According to screenshot #1 I way saying:

"Post a screenshot of browser.warnOnQuit set to true ..."

and according to screenshot #2 I was saying:

"... while TMP is active."

more options

TMP is very much is very much active i have not once disabled it. In fact many of my tabs are protected and styled through it as well so again my statement stands.

Ændret af NekoNekoMew den

more options

Hi NekoNekoMew

Please could you show what your about:config states about "browser.warnOnQuit"?

The requirement is running FF 17.0.1 and the latest version of TMP (you can use TMP 0.4.0.4.pre120724a or TMP 0.4.0.4.pre120724b).


Thanks,

Gary

more options

Today at 10:25 AM NekoNekoMew wrote:

so I'm just going to downgrade back to 16.0.2

Quite obviously this has already happened.


@gazzawazza:

He already did in screenshot #2, but guess what (see quotation above).

Ændret af FFmurphy den

more options

i ALREADY HAVE. I also said that even with 0.4.0.3 and 0.4.0.3.1 on 17.0 and 17.0.1 my settings were never set to false and the warnings did show up, 2ce, but never appeared again (i don't get how they appeared but i closed Firefox and started it up 2x in a row and both times i got the warning but the third time it went back to no warnings.nothing was updated or changed b4 or after hence my confusion). The only reason I'm saying this is because TMP is not the issue it's 17.0+, whether it says true or false warnings will not show up.

Ændret af NekoNekoMew den

more options

Can anyone else confirm this ...?

My confidence has slightly suffered.

more options

please look at the other person who said they had the issue or go to the TMP website forums ty.

more options

Please note that it was tested on firefox 18+ but it only got worse so they are attempting to patch around another Mozilla screw up.

more options

To rephrase my statement having TMP activated on FF17+ cause the screw up due to faulty patches/coding on Mozilla's part and the developer can barely keep up and at this point have no intention of racing against them any longer, hence why the next full update with fix is not being released until January.

Ændret af NekoNekoMew den

more options

Alas, you did not understand ... again. We're all quite aware of the issue with browser.warnOnQuit having no effect when TMP is active – in fact, that's because we're all here.

But: You are the only one so far who states that he got warnings under the circumstances described above.

Furthermore, you are the only one stating "TMP is not the issue it's 17.0+".

As opposed to that, I could NOT reproduce the faulty behavior with TMP being deactivated, which clearly confirms that it's NOT an issue of FF17.

It's a bug of TMP that just shows up with Firefox versions 17.0 and above. So far for the facts ... which have been approved in the forum of TMP like gazzawazza has posted ages ago.

Please stop spamming the thread with irrelevant / aforementioned stuff.

Ændret af FFmurphy den

more options

Then don't continually ask the same question.

more options

Which was ...?

more options

everyone giving their opinion on what i must obviously be overlooking even though i stated many times that everything is set to true.

Ændret af NekoNekoMew den

  1. 1
  2. 2
  3. 3
  4. 4