Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

How can we get the navigation buttons back?

  • 3 Antworten
  • 8 haben dieses Problem
  • 21 Aufrufe
  • Letzte Antwort von tim_mw

more options

How can we get the navigation buttons back? The standard browser that comes on my Note 3 has them. I don't want to access the menu every time I want to go forward and backward. The hardware back button is not designed for this purpose at all. If you hit the back button one too many times, it puts the browser in the background and throws you onto the home screen which is a behavior that nobody wants. We need these buttons: forward, back and refresh. It is utter nonsense to make a browser without them. The gesture add-on does not work well at all.

PS: Congrats on getting the HTML5 and video behavior right on a mobile browser. It is the only mobile browser that supports positioning in the video by dragging the progress bar while using the standard HTML5 video tag. The others all require arcane work-arounds to be added to websites.

How can we get the navigation buttons back? The standard browser that comes on my Note 3 has them. I don't want to access the menu every time I want to go forward and backward. The hardware back button is not designed for this purpose at all. If you hit the back button one too many times, it puts the browser in the background and throws you onto the home screen which is a behavior that nobody wants. We need these buttons: forward, back and refresh. It is utter nonsense to make a browser without them. The gesture add-on does not work well at all. PS: Congrats on getting the HTML5 and video behavior right on a mobile browser. It is the only mobile browser that supports positioning in the video by dragging the progress bar while using the standard HTML5 video tag. The others all require arcane work-arounds to be added to websites.

Alle Antworten (3)

more options

While the Note 4 is a reasonably large device it still falls into the phone layout bucket. We need this layout to function on very small screens some as low as 320 pixels high and 240 pixels wide. These sorts of devices don't have the space for a full toolbar.

more options

Thanks for your reply, but I don't see Firefox's position on this as tenable. Precious little browsing occurs on phones with 240 x 320 screens. This is not only because of their size, but because they don't have the horsepower to run Firefox without being aggravatingly slow. We serve 66 pages a second. There is no 240 x 320 traffic, a tiny amount of 480 x 800, and they don't use Firefox, and nothing of any significance until you get to 640 x 960.

We need 2 buttons, like the Samsung mobile browser, at the beginning of its address bar. Moreover, it is drop-dead simple to make the appearance of the buttons conditional, based on screen size.

Geändert am von IT_Architect

more options

I have this problem too, I really need the back/forward buttons on the title bar and in my opinion there is plenty of space for them on my phone which is a Samsung Galaxy Ace 3 (480 x 800 4 inch screen). The built in browser and Chrome both have buttons on the title bar and these work well.

The phones own back button isn't an acceptable substitute since I have far too often accidentally exited Firefox using it instead of going back.

Why can't this simply be a configurable option so that users can choose?

Alternatively, is there any way in which I can force Firefox to use the tablet style interface which does have these buttons?

Failing that does the extension API allow extensions to place buttons alongside the title bar if I were to attempt to write my own extension to fix this?