I have tried reloading and also tried the Beta version. I have a Samsung Galaxy S3 with Android Ice Cream Sandwich OS. Any suggestions will be greatly appreciated. Thanks
Is this a change? On the Getting Started page it shows these buttons. sing the android menu button seems like an extra step especially to use the back button. Also it doesn't have a button for home or settings.
The back button for Firefox is just the Android back button. There is no need to bring up the menu to go back.
After you press the menu button you can pan the Firefox menu list to reveal the settings option. In Firefox 18 we have compacted the menu so that scrolling should not be needed.
Firefox for Android fits in with the Android OS versions. Android 4.x provides more flexibility in the menu design that in Android 3.x - 2.2. Thus we've use that flexibility to design a menu similar to other Android 4.x apps such as the stock browser, Chrome and Google+.
I am using FF18 on Android 4.1.1 on Samsung GS3 (SGH-I747M).
When I hit the back button, if I am already at the first page in the current tab, I am exited from Firefox. This happens the same whether I have one tab or several tabs open.
When I have multiple tabs open, rather than exiting FF, it would be more useful to revert to the tab selection screen, or to another tab. In fact, the tab in question may well have been created by another tab, so exiting FF is probably not what the user intended. No on-screen indication is given that this 'exit' will occur on 'back'.
Does it work this way because FF is using the Android back button instead of a FF back button? If so, would it make sense to implement a FF back button?
If there is no more back history then the app should be placed in the background, this is standard Android behavior.
The point is that there is back history; just not on this tab.
I did not open the tab. I clicked on a link, which opened the tab. I did not even notice that a new tab had been created. I hit back, expecting to go back to my original page. Instead, FF exited.
The inconsistency is that when I click the back button, sometimes FF takes me back to the previous page, and sometimes FF exits instead.
It would be more consistent to close the tab if there is no more back history.
Chrome on Android has the same behavior. As does the Stock browser for devices before Android 4.2.
We try our best to match platform conventions. We can't go about making our own UI interactions and be a well respected or well understood Android app.
At the distinct risk of embarrassing myself, I post this followup.
I tried FF18 again just now, and it works as I would prefer: 1) if a tab was created by clicking on a link, then when the back history runs out, the tab is closed. 2) if a tab was created by me, then when its back history runs out, FF 'goes to background'..
To be perfectly clear, it does not exhibit the behavior I was observing yesterday. I really have no explanation for the change in behavior.