User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20100101 Firefox/17.0 Build ID: 20121128204232 Steps to reproduce: Upgraded from Firefox 19.0 to 20.0 Actual results: The Quit menu item is not available anymore Expected results: The Quit menu item should be kept. Release notes suggest: "When done browsing just tap Home or Back". "Home" means minimize the application, this is not what I need. "Just tap back": really? Do I have to rewind my whole session by typing back 20, 50, or 100 times? For now I have to do what I do for all those non ergonomic apps: kill it in the task manager. This removal is a *regression*. Any application should have a Quit button (even if 90% don't). What do people complain about their phone/mobile device? Slowness and battery life. What is the effect of removing the possibility to quit the application? Degrade device performances and battery life. Furthermore this make things (how the device works and behaves) harder to understand for standard user. Its experience is already getting worse (have a look to users feedback about this release...). Please don't redirect me to the QuitNow extension. This is not the point here, I am speaking about a native way to quit cleanly the application. Plus, experience shows that sooner or later such application will get broken.

I'm really sorry this is causing you grief. In addition to following the OS guidelines, we feel that most users do not use a Quit menu on Android. Firefox supports add-ons to allow people to add functionality that is not part of the core application. This is a perfect use case for an add-on.

For those curious, re system guidelines see: http://www.youtube.com/watch?feature=player_detailpage&v=631T7B8HOv4#t=186s

(In reply to Mark Finkle (:mfinkle) from comment #1) > I'm really sorry this is causing you grief. In addition to following the OS > guidelines, we feel that most users do not use a Quit menu on Android. > > Firefox supports add-ons to allow people to add functionality that is not > part of the core application. This is a perfect use case for an add-on. The app is now disallowing closing in a regular way ( the back button ). Even when no tabs are open the application is not closed (Chrome which also follows this idea closes when no tabs are open). So an user will have to go to the task manager to "force" close the browser. This results that Firefox occupies memory of the phone/tablet which might result in a bad user experience.

(In reply to Mark Finkle (:mfinkle) from comment #1) > I'm really sorry this is causing you grief. In addition to following the OS > guidelines, we feel that most users do not use a Quit menu on Android. You can't just make such decisions based on a feeling. I never use the "Home" button (I Quit or go Back-Back-Back), but I won't ask the manufacturer to remove it. I am wondering if there was is discussion page or mail thread where this decision was discussed (there must be, for me it is the most important change between versions 19 and 20). Firefox used to be a leader on the web experience and fought against bad developper habits e.g. by forcing them to go back to standards. Now you are told that users are too stupid to make the difference between closing an application and letting it in background, and you just follow blindly this philosophy. I am so disappointed... Will Mozilla also forbid "Exit" buttons in Firefox OS? > Firefox supports add-ons to allow people to add functionality that is not > part of the core application. This is a perfect use case for an add-on. I disagree, because quitting an app is a fundamental need, not some extra request for a small fraction of advanced users which will smoothly forget about it with time.

The Google Android designers explain why apps should not have a quit button in http://www.youtube.com/watch?v=631T7B8HOv4