@zopiac Are you talking about Opera 60 or Opera 12.18? I could not see the option at all in Opera 60, and the order in Opera 12.18 is Left to Right when scrolling down, as it is in Vivaldi.
I suggest using "Display Tab Cycler as List" then the up/down order is obviously correct.
There is no harm in asking for an option to change it, but with the list you may decide that you do not need it. You can also see a lot more tabs in this mode.
Yes, please! I would like to see a draggable scroll bar in Vivaldi Android. Sleipnir has it, Opera I heard has it, Samsung Internet has it as well. The best implementation is Sleipnir though since you can drag anywhere on the right side and it takes you there and you can keep dragging to scroll (similar to Windows).
Of course, this is to be a setting as perhaps not everyone wants this.
This is very important for quick navigation as it's tedious swiping up or down on long pages.
@coronium , yes I know that most smooth scroll extensions don't work well in Vivaldi, the only one which works as it should is the Chromium wheel smooth scroller, but it's closed source from Chrome developers.
Well this has at least confirmed I am not going mad.
I use a wacom tablet a lot on my machine, and occasionally its in front of me when browsing, but i cannot easily scroll up and down pages using it
I was convinced there used to be a way in vivaldi of being able to scroll and pan with the mouse button alone (so an action i could assign to a vivaldi/wacom script so my pen could be used to pan and scroll)
appears while i remember the action, it was way further back in time than vivaldi and was an opera thing 🙂
I would definitely use this if it were available as a keyboard shortcut, too, and for left/right scrolling as well. Currently there are PgUp/PgDn keyboard shortcut commands available, but I'd like to use j to scroll up, k to scroll down, h to scroll left, and l to scroll right (this matches scrolling behavior from vi/vim).
I've merged discussion on this topic from a number of different places.
Also, the devs have indicated this is an "upstream" issue - I.e. it is one for chrome to fix and vivaldi unfortunately has no control over.
If you are active in chrome/chromium's feature requests you could ask there instead.