Question

hi Cor-el

This is when closing a window.

I've just tested "closing other tabs" via mouse context menu and that does generate the warning.

Regards,

Gary

If you close a window and that is the only browser window then you may not get a warning because session restore might be enabled to reopen the tabs on a next start.

• Tools > Options > General > Startup: When Firefox Starts: Show my windows and tabs from last time

Hi Cor-el

I'm afraid it's not that, since FF is configured to open on my homepage.

However... and apologies for this - the first thing I did was check in safemode / with addons disabled - but it appears to be a problem between FF17 and Tab Mix Plus.

If you go into About:Config with FF 17 and TMP active (even using dev builds 0.4.0.4pre.120724a and b versions), "browser.warnOnQuit" is set to false and locked on false I.e. you simply cannot change the boolean value.

However, if you disable TMP, I found "browser.warnOnQuit" still set to false (i.e. hence why the no warning on exiting multiple tabs problem was still replicated in safemode) but at least you can change the value.

The dev(s) are aware of the problem but I'm not aware of a fix date.

Regards,

Gary

Just to clarify:

"However, if you disable TMP, I found browser.warnOnQuit still set to false (i.e. hence why the no warning on exiting multiple tabs problem was still replicated in safemode) but at least you can change the value."

As soon as you re-enable TMP, browser.warnOnQuit is set from true back to false and locked again. Therefore, unfortunately, setting this preference to true in safe mode does not solve the original problem.

Is there any way to lock this preference yourself (once you've set it to true), preventing TMP from setting it back to false?

Hi FFMurphy

The point I was making about being able to set the WarnOnQuit config to true was that my original conclusion regarding FireFox was wrong i.e. without Tab Mix Plus being active, the warning regarding multiple tabs closing functions correctly.

As I said, the TMP devs are aware of the problem but a fix date has not been confirmed. It's been suggested on the TMP forum that we may see a new build in January. Whether a fix will be part of this build is not known either.

I'm not aware of a way to lock WarnOnQuit to true, I'm afraid.

The peculiar thing about this issue is that if you have multiple windows with multiple tabs, the warning works... until you get down to one instance of FireFox.

The other point is that the latest dev build of TMP works fine with firefox 16, so clearly something has changed with FireFox 17 (and 18 - someone has confirmed the same issue with the pre-release build of FF18) i.e. whether TMP doesn't work properly because of a bug or whether it's simply to do with something having changed in FF and TMP has to change to fall in line, I don't know.

Regards,

Gary

Hi Gary,

I was fully aware of what you pointed out in your previous post, but just wanted to clarify also for others following this thread that although it is possible to set the preference back to true in safe mode / with disabled TMP (like you said), this only lasts until TMP is re-eabled and therefore should not be mistaken as a solution (like I nearly but not eventually did).

Also I'm following the according thread at the TMP forum myself, being not too optimistic about another dev build resolving the issue before January either. Hence I'm back on FF16 – also due to another bug concerning FF17 creating invalid icon files when creating drag & drop internet shortcuts on the desktop of Windows XP systems including SP3, which is another story.

As for the inconsistent behavior with multiple windows (still one instance though) of FF17, I already discovered the same thing right after updating previous posts [here] and [here] assuming that this would solve the issue, but since it is at least TMP related (despite not occurring with FF versions previous to 17&18) I didn't contribute any further on this side effect here.

Thanks for the info regarding FF18, as I was about to update with a glimpse of hope, before deciding to downgrade because of the aforenamed reason.

Having skimmed through the release notes as well, not seeing any changes to warnOnQuit after FF13, but lots of trouble with warnOnCloseOtherTabs according to Bug 277079 and Bug 772319 (which you mentioned, also being discussed in the first thread I linked to above), however, I'm equally unsure about who's to blame in the end. To my notion, the impacts of both settings in the preferences weren't only inconsistent, but also didn't actually reflect the option menu choices anymore in FF17. Now having banned this version I can no longer investigate these issues to specify them in detail, of course.

Cheers, murphy

I have this problem too. i have tab mix plus but in my case browser.tabs.warnOnCloseOtherTabs and browser.tabs.warnOnClose are both set to true but i still get no warnings which sucks because i accidently click on close alot.

That's rather clever. How did you manage that (getting those configs to those settings)?!

Could you post your build versions of FF and Tab Mix Plus?

Weird that you've got your config to those settings and it still doesn't provide warnings on close...

Can you confirm what happens if you disable TMP, then try to close multiple tabs? It should warn you. If not, double-check the about:config settings already mentioned...

Cheers,

Gazza

Can you check some of the tabmixplus about:config settings too?

What about:

"extensions.tabmix.tabs.warnOnClose" "extensions.tabmix.protectedtabs.warnOnClose" "extensions.tabmix.warnOnclose"

Cheers,

Gazza

Firefox 17.0.1 Tab Mix Plus Dev-Build 0.4.0.4pre.120724a (i had 0.4.0.3 and 0.4.0.3.1 as well same thing) and i did nothing they say both say true and i can change the values to false and back w/o any issue. the warnings just don't appear for me since 17.0. And ik TMP causes the no warning thing but in my case it says true not false

All say true

If you have Tab Mix Plus then that extension will override the default Firefox settings that show in your screenshot.
It is best to search for warn to see all "warn" related prefs including the ones added by TMP.

Again all set to true. i

It's firefox 17's fault for being incompatible. i just decided to downgrade back to 16.0.2 and hope that the developer can keep up with these ridiculous excuse for updates.

weird it's finally working. so nvm i guess

Hi NekoNekoMew

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

browser.warnOnQuit

The browser.tab ones are fine with me too (i.e. can be changed).

So, just to confirm, you've managed to get everything working with 17.0.1 or did you have to roll-back to FF 16 to get the warnings back?

Regards,

Gary

I upgraded to 17.0.1 and for a time it seemed to be warning me again; However, it stopped as of this morning and from what i can tell nothing changed. most likely the warnings were a glitch :( so now i'm not being warned again.

so I'm just going to downgrade back to 16.0.2

Goto Tools -> Options -> Warn me when closing multiple tabs (check/tick that)

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

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

@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.

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?

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

"Isn't reading fun :3?"

Yes ... if you can.

You were saying?

Anywho, like i was saying reading is fun :3

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."

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.

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

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).

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.

Can anyone else confirm this ...?

My confidence has slightly suffered.

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

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.

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.

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.

Then don't continually ask the same question.

Which was ...?

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

And they are or where posts/forums on the issue but they have since been edited/deleted because I'm the 3rd person I've seen, in person, with my issue. My mom's and my sister's computer has it too. there is a post about it i just have to go find it.

You only stated many times that your warnOnClose settings are set to true, until you were asked for the 42nd time to post your setting of warnOnQuit.

When you finally did, I did not ask "everyone to give their opinion", but anyone else to confirm that "TMP is not the issue it's 17.0+" like you said.

Which is false according to the observations of gazzawazza and myself.

What i meant was TMP itself was not the issue an incompatibility with changes in FF17+ which is why it has to be disabled because the two just don't mix.

Mozilla is not responsible for the correct operations of add-ons as long as the given functionality is not affected without the add-ons being activated. Which is, again, applicable in this case.

As for the sentiments according to their update policies (and side effects), please refer to the statements in my posts on the first page of [this] thread. That should say it all.

hi Murphy

Interesting development:

Got a report that TMP dev build tab_mix_plus-0.4.0.4pre.120724b and FF 18b2 correct the warning problem.

http://tmp.garyr.net/forum/viewtopic.php?p=59021#p59021

I've not tested it myself though.

Please note the above dev build breaks the TMP options in FF17.0.1 but apparently is ok with FF18beta2.

Cheers,

G

Thanks for the news, Gary!

Please let me know once you got a confirmation or you've tested it yourself, because I don't wanna mess around with different versions too much until it's known to be safe to upgrade from 16.0.2 again.

So long, murphy

Hey Murphy

Confirmation is as per my link - it appears to be working for the admin on the TMP forum.

However, I've not tested it myself ;)

Tbh, I don't like mucking around with betas unless I've got a specific problem to address, which can't wait (as you know, betas can fix one thing then break another).

The scheduled release of FF 18 is for week beginning 6th Jan, so was just going to grin and bear it. Also, I'm getting used to the no warnings on closing!

If I was in your position, I'd stick with FF 16.0.2, unless there are any security fixes in 17, which make it important to update.

Here are the summary release notes. Scanning the list I can only see an HTML5 security adjustment.

http://www.mozilla.org/en-US/firefox/17.0/releasenotes/

FF 17.0.1 doesn't seem to do much but I've only given the list a superficial scan:

http://www.mozilla.org/en-US/firefox/17.0.1/releasenotes/

All the best,

Gary

I meant a confirmation OF the information in the thread you linked to, which didn't seem that much reliable to me but rather a bit confused.

Indeed I'll stay on 16.0.2 as posted before, because it would happen to me too often that I would close windows with more than a dozen tabs open :|

As for the possible security problems, I was also considering that in the thread I referred to in my previous post ... I'm not surfing too risky ;)

Maybe we'll meet again in January, happy holidays!

murphy

??? you mean you actually get a warning when you close multiple tabs with TMP? We haven't seen a close-multiple-tabs warning with TMP installed since FF3.6.

Yes, with FF 16.0.2 it's absolutely no issue and works like charm.

My experience,

1. Install firefox 17.0.1.

2. Test "warn me before closing multiple tabs". It should be ok.

3. Restart firefox. Open three tabs.

4. Use panorama . Move one tab to a new tab group.

5. Quit firefox. And you will find "warn me before closing multiple tabs" doesn't work now. And it won't anymore unless you reinstall firefox. (Even the "reset firefox" can't help.)

I saw an useful answer by Fanolian on Moztw.org forum.

The panorama issue seems related to this one. https://bugzilla.mozilla.org/show_bug.cgi?id=709579 Which mentioned "Closing multiple tabs warning doesn't work correctly when the "Show my windows and tabs from last time" option is selected".

After installing firefox and using panorama the first time, the "When Firefox Starts" item will be forced to be "Show my windows and tabs from last time". (Is this a right reaction?) Thus, after using panorama, consequently, "Warn me when closing multiple tabs" doesn't work.

@NotarySojac i have have always received a close tab warning with TMP enabled till 17.0.

hi all

Tab Mix Plus Dev-Build 0.4.0.4pre.121214a resolves the no warning issue.

Tested with FF 17.0.1

Cheers,

Gaz

I have the same problem.

TMP is NOT the reason, because I don't use it.

All worked fine until FF 17, so a FF 17 bug seems to be the reason.

I wonder, that this fault is not detected automatically in the regression tests, because start / stop and read / write config are the most basic necessary functions.

I'm noticing this issue too. I've never used TMP and have all my other add-ons disabled. I have my browser.warnOnQuit set to true, yet when I go to File > Quit, I'm not warned. I noticed this on Firefox 19.0.2 on 64 bit Linux and Firefox 19.0 on 64 bit Win 7.

hi Dgmdan

I've replicated your problem on FF 19.0.2 on Vista 32bit, both using TMP and in safe-mode i.e. NOT using TMP.

Please note that if you use the window close button (top right), the warning DOES appear.

Regards,

Gary

Thanks - so can this be considered a bug? It seems like browser.tabs.warnOnClose=true has the desired effect but browser.warnOnQuit=true is ignored. I run into this a lot because I use CTRL+W to close a tab but I'll occasionally hit the wrong button and do CTRL+Q instead, as the keys are next to eachother. This closes the whole browser without a warning.

Hey Dgmdan

Did a quick search. 3 listed entries on the matter:

https://bugzilla.mozilla.org/buglist.cgi?quicksearch=warnonquit

I think all are still open but don't look like they've been allocated.

Comment 9 here:

https://bugzilla.mozilla.org/show_bug.cgi?id=502908

Points to here:

https://bugzilla.mozilla.org/show_bug.cgi?id=550559

which has been assigned.

Tbh, it's a bit painful wading through all the detail to answer your question with certainty but the problem is documented and bug 550559 is at least assigned.

Finally, and most importantly, there's a workround listed under bug 550559 / comment 27:

https://bugzilla.mozilla.org/show_bug.cgi?id=550559#c27

Workround is via an add-on. I've NOT tested it so am making no assurances whatsoever. However, feedback seems to be that it works:

https://addons.mozilla.org/en-US/firefox/addon/always-ask/

Regards,

Gary

I am a hardcore firefox fan since the days of firefox 2.0. I have celebrated with ,y college mates when firefox 4.0 was released and there was this art showing the map of the world with statistics about number of downloads.

I always update firefox to latest stable build as soon at is available and at the time of writing this comment, 20.0.1 is the latest stable build. I am running windows 8 32 bit on dell vostro laptop.

Now, I have been experiencing this bug since the day firefox 4.0 came. I want to tell the motherfucker developers that do your fucking job and solve this simple looking bug. I am sick of reading comments suggesting users to tick the option in the "tab" section. We are not dumb you asshole !!! Firefox is for power users like many of us and most of us also know how to use about:config to set those three tab related option to true. If you Google a particular phrase "Firefox closes without warning" (http://bit.ly/12Sx3I3) you will find at least one post describing this bug for every firefox release and every post has similar kind of answers. WTF, are you doing developers :X :X :X. Some of the comments say that this is happening because of some shitty tab related addon but in my case I don't have any such addon and even if some shitty addon fucks my firefox setting why ain't I be able to restore it by ticking the option from options dialog again and why that is not getting unticked automatically as soon as some addons fucks with it.

So, finally, let me tell you my observation which I think can be helpful to debug this problem in the future releases of the firefox. One of the comment says to select option that says "Show my windows and tabs from last time" in general section of options dialog. I am very much concerned about my privacy and I don't want some motherfucker government or company to hijack my session and still my cookies and browsing history etc. which is why I always run firefox in private browsing mode which I have ticked in privacy section of options dialog. I have also tried to use never remember history options in the same section. Both of these option disable the option I mentioned in the first statement of para. So developers, you need to focus on that part as I can't think of any reason for relation between privacy/session settings and warning while closing multiple tabs by mistake. Another important observation is that if multiple windows of firefox with multiple tabs in each window, are open this bug does not occur if I try to close one particular window which may have one or more tabs open. Some of the comments I have read before suggests to reset firefox profile folder which I guess is equivalent to fresh installation of firefox. In that cases, surely this issue is resolved but that is just for very short duration of time. This bug occurs again irrespective of the ff version you are using and how many times you have repeated resetting your profile.

I hate myself to comment in such a harsh manner but that's how much frustrated I am right now because of this bug. I am also a software developer and if you have read my comment till this point and you contribute to the firefox project than please try to resolve for the sake of our beloved firefox.

What is the startup setting?

• Tools > Options > General > Startup: When Firefox Starts:

If you use 'Show my windows and tabs from last time" then your session should be restored automatically and in this case Firefox doesn't ask for confirmation.
You will have to select one of the other two (Show my home page or Show a blank page).