Snapshot 1.0.283.8 - Fixes to typed history, keyboard shortcuts for web panels and visual polishing
-
oh thanks! Will add it to my notes
-
I think synchronization in browser will be not too soon.
So better way for now is using extensions for synchronization. -
when you click on "close stacked tabs" (something like this) to close the tabs in tab stacking and instead of it, is closed the other tabs but the stacked tabs.
win 7 64bits
anyone confirm? -
Known. Being worked on.
-
I see. Let's hope they will get fixed in some near time. In the meantime, as you now know they are tracked, I would say there is no much need to remind about them, at least not every time.
I noticed you said 16+ rows, still I was unable to reproduce it. Does it matter how many columns (does it happen with 1 or 2) or resolution? Could you provide a screenshot? Maybe please resubmit this bug details under comments in the upcoming snapshot, which may come today/tomorrow - so that we stay on top with this issue.
-
Confirmed. Could you report it and provide bug number here?
-
I've got trouble with flickr - just opened up some tabs in the background via compfight.com (a flickr-search tool which helps for low bandwith) and couldn't switch tabs anymore. For my installation it's a reliable way to crash some part of Vivaldis UI, can anyone confirm?
-
Bug reported. Bug number: VB-9507
-
What do you mean? What is Maj and Verr Maj?
-
It is tracked.
-
It is tracked.
-
Thank you. Very good description.
Passed over so that it is looked into. -
Yep. He he, I get this as well. Seems there is a very hungry shortcut set up. Disable it from Settings | keyboard | Mail for now.
-
What else can I write about your post than exactly! and thanks!
-
http://www.franceinfo.fr/player
it doesn't work- no sound - it worked on previous snapshots.
latest snapshot, linux -
Then you will be even more happy really really soon. ;-D
-
You need an packet from chromium, which isn't anymore included in Vivaldi for legal reasons:
in this packet is an file named libffmpeg.so, which is needed in /opt/vivaldi-snapshot/lib
After a restart of the browser it should work (it does for me)
There is a link in the changelog which explains more. -
This Chromium bug will be fixed in the upcoming snapshot.
-
OK, I have consulted on the feasibility of fulfilling your request and please find the following insights.
1. The suggested line of code does not have cross-platform effect. It would require different changes per platform. So it is not a quick fix as much.
2. Context menus is a sensitive part of the User Interface where accessibility issues need to be taken into account. Bright red is a big no as a default here, eyes will bleed for some users. Blue is quite a common standard, also when you look for example at Opera 12, though just the shade is a bit different. As a target solution browser should by default reuse user's system colour scheme. There is also no need here to be different just for the sake of being different… The menus actually should look and feel the same between browsers considering accessibility/discoverability aspects - so that users don't have to re-learn how to use these basic interface elements.The conclusion is that it is neither a quickfix, nor red is the way to go by default. The menus will get rework with time when we switch from Chromium menu components to our own. On top of this you will be able to change the colour to your liking when we reach this level of customization, which we will hopefully reach at some point of time (however no sooner than when we have our own menu components).
I hope you will approach to it with understanding and you find this feedback satisfactory. Cheers!
-
removed - it was meant to be a reply to the comment below.