add reload and back button to line with address bar
-
These two are used frequently and would be great to have them on onlick access.
-
Or option to add them would be fine, if possible.
-
The back button is already exposed in the UI on the bottom toolbar, as well as a forward button. These two buttons are on either side of the speed dial button. So that's already immediately available.
For the refresh button, I don't see any need to move it from its current location. There's already very little space to show the address of the page, it's rare that it doesn't get truncated unless you're on the root of a domain. Not only would it clutter that space, further reducing the visibility of the address, there would be very little, I'd say insignificant, gain in usability.
The refresh button sits directly under the Vivaldi button that loads the menu at the end of the address bar. Effectively, the refresh button is already on the toolbar, it just requires a double tap instead of a single tap. Once you realize this, you gain virtually nothing by pulling the button out of the menu in order to have it perpetually visible, yet you lose space on an already limited toolbar.
In fact, I would say that moving refresh out of the menu would make it more difficult to use. The upper right corner where it currently sits is a very natural position to move my thumb; almost every app has an important button there, typically the menu button. So I, and I imagine a large percentage of users, have a muscle memory that goes to that position. I don't even look for the refresh button -- I just tap tap and the page refreshes. If it were moved, then I'd have to look and fight muscle memory in order to use it.
The current design seems to be optimal, once you realize that you can think of the Vivaldi icon as the refresh button. Just tap tap and you've got your refresh. In short order you'll be doing it without even noticing like I do.
-
I don't know about you, but I can't see any reload button (tablet mode). Fortunately I have a real keyboard and can press [Fn] F5, though having to hold [Fn] is inconvenient.
-
I'm not certain what you mean by tablet mode. Do you mean with the "Show Tab Bar" setting enabled? The screenshot below is with that disabled but it doesn't change this -- the refresh page button is still directly under the Vivaldi icon, and inline with/effectively on the toolbar with the address field. It's called "Refresh page" rather than "Reload", but same thing.
As you can see, it's on the same line as the address field. So you can think of the Vivaldi icon as the refresh button. Just tap tap and the page will refresh. The effort to tap again in the same location is hardly significant, especially in comparison to reaching for a different position than the spot one clicks in countless apps to access important functions.
Apps commonly put either the menu icon like Vivaldi, or a very commonly accessed button like the shopping cart in Amazon Shopping, messenger in Facebook, search in Audible, etc. So users have built muscle memory to tap that spot. To refresh in Vivaldi, you just tap twice. It's hard to imagine making it easier to access, and moving it would be at the cost of making the already short address field even shorter.
-
This post is deleted! -
This post is deleted! -
@BoneTone When the Address bar is set to be displayed at the bottom, I have completely lost the back/forward button with a possibly to display the list of previously visited sites (using the long tap). I can configure Vivaldi, to show the back/forward button on the main Vivaldi menu, but those buttons don't implement the long tap feature.
Is there any alternative to reach the list of previously visited sites in the current tab, please? If not, it's a deal breaker for me, even though I would prefer to have the Address bar at the bottom.
-
Thank you for your request. As this post has had less than 5 votes over 4 years it will now be archived. If something still isn't working or is missing, you can open a new thread or search to see if a newer one has already been opened.
-
LLonM moved this topic from Mobile Feature Requests on