My main gripe is that there is no back button (to return to your previous page) anymore.
At this point, I think Google has made continued executive salaries at Mozilla dependent on making the worst possible browser. They view these complaints as evidence of a job well done.
I'm still on 68, but the only back button i ever use is the android 'back' navigation button, not the browser "back button".
Did they remove the "three dots -> back arrow" ? I can't recall the last time I used that. Who uses that back arrow? Is it something to do with the model phone where the built in android back button isn't present??
(I DO occasionally use the 'three dots -> forward button' though. To go forward after having gone back.)
I tend to like having a back button because of the relative unpredictability of the Android OS back button. The OS button can back you out of the app altogether; a regular back button is clearer in its function. That's one typical annoyance about Android; in my experience, sometimes the back button is interpreted as "previous app" rather than "previous screen of this app" or "prior/higher screen or menu on this app." Thus, for example, in Samsung Messages pressing the OS Back from a message thread always exits the app rather than going to the inbox, even if you were just there.
On Android the back button is ALWAYS "back to the previous view". So if you follow a link in an app and it opens in the browser then the back button will take you back to the app. If you follow a link in the browser the back button will take you back to the page the link was on.
I don't know how Samsung managed to break that but I suggest moving to a different messaging app that doesn't deliberately break the UI. Certainly Google's various messaging apps behave as expected.
Riiiight, Android "always" does (insert any possible action here, duly noting that you are an idiot for stating 'always')
Android is unpredictable in consistently unpredictable and bizarre ways. Like Mozilla, if something is a useful convention that users rely.on, just give it time and they'll "fix" it with a regressive update.
I'm not speaking to this most recent release of FF because FF for android has been a lost cause since its inception and nobody gives a fuck, just speaking in general as a disgrunt
No, the GP's right. The back button may be intended to mean "Back to the previous view", but it's so unpredictable that after a while many of us avoid it. Sometimes it'll back out of the application if pressed enough times, sometimes the developer's idea of "previous view" is unintuitive. I brought a menu up - does it close the menu or does it bypass the menu completely and go to the home screen of the application? Sometimes the application has tabs, like in a typical more complicated settings page for an app, so you do something like (Main application home page) -> Settings, click on the "Advanced" tab, hit back... and it takes you to the Main application home page.
Even if all developers were on the same page about what back means, there's enough of a disconnect between intuitive concepts of what the previous view is and what a developer may feel is technically the previous view for it to frequently be unpredictable what it does. And after a while, that kind of unpredictability generates frustration and a desire to avoid the key altogether.
And, FWIW, I would never have assumed that the system back button would go back in my browser history except that I've accidentally found that out trying to quit the browser. Because what you and Google are saying is a "view" in this instance isn't intuitively a "view" to me. The web browser showing-a-document thing is a view intuitively. The application shows the web, it isn't the web itself.
The problem is that a user can't tell the difference between a click that stays on the same page vs one that takes you to a new page. With the browser back button, at least if you think you clicked a link to a new page and are wrong, the back button will (at worst) take you to a page you previously visited. The OS back button might take you to a different app. With the browser back button, at least you stay in the browser when you realize your mistake.
Yes, the three dots back arrow was convenient to have because it doesn't do anything else, unlike the android back button.
I'm currently running F-Droid Fennic, which is the old version of Firefox as served by F-Droid. Mainly because I used a number of addons, youtube playback has garbled audio at faster speeds on the new version, and tabs can't be reordered anymore. Ugh.
One problem solved, and not even one of the most annoying ones. I'll keep using Fennic until a non-beta firefox supports the addons I use and can play youtube videos at 1.25x without sounding like complete crap.
"There are things that are so serious that you can only joke about them"
- Heisenberg
Da fuq (Score:2, Funny)
My main gripe is that there is no back button (to return to your previous page) anymore.
At this point, I think Google has made continued executive salaries at Mozilla dependent on making the worst possible browser. They view these complaints as evidence of a job well done.
Re:Da fuq (Score:2)
I'm still on 68, but the only back button i ever use is the android 'back' navigation button, not the browser "back button".
Did they remove the "three dots -> back arrow" ? I can't recall the last time I used that. Who uses that back arrow? Is it something to do with the model phone where the built in android back button isn't present??
(I DO occasionally use the 'three dots -> forward button' though. To go forward after having gone back.)
Re:Da fuq (Score:5, Informative)
Re: (Score:2)
On Android the back button is ALWAYS "back to the previous view". So if you follow a link in an app and it opens in the browser then the back button will take you back to the app. If you follow a link in the browser the back button will take you back to the page the link was on.
I don't know how Samsung managed to break that but I suggest moving to a different messaging app that doesn't deliberately break the UI. Certainly Google's various messaging apps behave as expected.
Re: Da fuq (Score:1)
Re:Da fuq (Score:4, Insightful)
No, the GP's right. The back button may be intended to mean "Back to the previous view", but it's so unpredictable that after a while many of us avoid it. Sometimes it'll back out of the application if pressed enough times, sometimes the developer's idea of "previous view" is unintuitive. I brought a menu up - does it close the menu or does it bypass the menu completely and go to the home screen of the application? Sometimes the application has tabs, like in a typical more complicated settings page for an app, so you do something like (Main application home page) -> Settings, click on the "Advanced" tab, hit back... and it takes you to the Main application home page.
Even if all developers were on the same page about what back means, there's enough of a disconnect between intuitive concepts of what the previous view is and what a developer may feel is technically the previous view for it to frequently be unpredictable what it does. And after a while, that kind of unpredictability generates frustration and a desire to avoid the key altogether.
And, FWIW, I would never have assumed that the system back button would go back in my browser history except that I've accidentally found that out trying to quit the browser. Because what you and Google are saying is a "view" in this instance isn't intuitively a "view" to me. The web browser showing-a-document thing is a view intuitively. The application shows the web, it isn't the web itself.
Re: (Score:2)
Re: (Score:2)
Yes, the three dots back arrow was convenient to have because it doesn't do anything else, unlike the android back button.
I'm currently running F-Droid Fennic, which is the old version of Firefox as served by F-Droid. Mainly because I used a number of addons, youtube playback has garbled audio at faster speeds on the new version, and tabs can't be reordered anymore. Ugh.
Re: Da fuq (Score:2)
Or using 79.0.5
Re: (Score:2)
One problem solved, and not even one of the most annoying ones. I'll keep using Fennic until a non-beta firefox supports the addons I use and can play youtube videos at 1.25x without sounding like complete crap.