Closed Bug 1274724 Opened 9 years ago Closed 8 years ago

firefox has no confirmation dialogue for closing

Categories

(Firefox :: Untriaged, defect)

46 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 502908

People

(Reporter: illumilor.e, Unassigned)

Details

(Keywords: qawanted)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0 Build ID: 2016042500 Steps to reproduce: Whenever hitting ctrl+q there is no confirmation dialogue for multiple tabs, even though in settings there should be confirmation. It just quits
can you try visiting about:config and then toggle these settings and see the difference please browser.showQuitWarning browser.warnOnQuit browser.tabs.warnOnCloseOtherTabs browser.tabs.warnOnClose Thanks
QA Whiteboard: [testday-20160520]
Flags: needinfo?(illumilor.e)
None of those worked.
Flags: needinfo?(illumilor.e)
Keywords: qawanted
Hello Reporter, I tried duplicating this issue. I didn't see the problem in FF 44.0 with my current profile. However, as soon as I upgraded my FF to 46.0.1, I could reproduce the problem with my existing profile. However, as soon as I created a new profile, FF showed the expected warning window on CTRL + Q when browser.showQuitWarning and browser.warnOnQuit settings were set to "TRUE". If you have not tried so, can you please try with a new profile after ensuring about:config settings and let us know your findings? Below is a link on how to create a new profile: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles Tested on: User Agent Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0 User Agent Mozilla/5.0 (X11; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0
Flags: needinfo?(illumilor.e)
One of the two was already set to true, but setting the other to true seems to give some session restore dialogue when pressing ctrl+q
Flags: needinfo?(illumilor.e)
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.