Snapshot 1.0.201.2 Improvements to Search Engine Management, Spatial Navigation, Gray look and the foundations for customisable mouse gestures
-
Exactly!!
-
Granted, it isn't a Microsoft-sized operation, but marks would already be helpful. While some team members may be more recognizable due to handling a lot of the work of interacting with the userbase (e.g. Mr. Arnason, "olli"), with 29 (and counting) employees, surely you don't expect most users to keep entire track of who's who (by screen name).
Additionally, there are a handful of current users I've seen who may be mistaken for team members, because those users stay very abreast of developments and post a lot, but who are (unless I'm mistaken) not actual Vivaldi employees. While those users' comments are generally very helpful and commendable (and perhaps those extra-helpful users could even be granted recognition with some other badge on their avatar or next to their name), I think it would be nice to have a clear indication of when statements are being made by those who can speak most authoritatively, and I second that the clearest way to do that would probably be with an overlaid-on-avatar or screenname-traling "[v]" badge.
-
Short update: Unfortunately we're still having some issues that need to be addressed. If no further regressions show up, you will get the new snapshot tomorrow. :idea:
-
Thanks for the heads up.
-
@Piter432:
Hmm, you're right. That makes sense
Thanks.
Cheers! -
Thanks for the notes. See? That helps a lot!
Well, since the new snapshot isn't coming out today, I'll take this opportunity to say now what I meant to in the next release. Opera 12 had a function that made sure link would open in the same active tab when left-clicked, even if the link would open a new tab. I believe this was called "use active tab" or something like that. I really wish for that function back, because when I left-click I want to open the URL in the tab I'm using! If I wanted to open a new tab, I would use the middle-click!
Please, make this happen. This is really annoying for me!
-
I would love to see the pan window shortcut like in Opera 12x (ctrl+alt + mouse)
-
+1
-
Hello, any news?)
-
OK, it turns out there actually was another severe regression. We need to delay one more day. Sorry guys. Please bear with us.
-
sounds good to me. Thanks!
-
I still have the problem that changing the keyboard shortcuts affects the mouse gestures. When I redefine new window as (shift+ctrl+n) and add (ctrl+n) for new tab, the mouse gesture for new tab stops working and closes the tab instead. I reported this ealier, hope it gets sorted out with the mouse gesture customizations. Would love to use Vivaldi for everyday browsing.
-
Thanks for letting us know. We really appreciate your keeping us updated. Hope you can fix it.
-
Thanks for the update. Simple updates like this are really welcome.
-
I think it might be an update in chromium?
-
https://www.privateinternetaccess.com/blog/2015/06/google-chrome-listening-in-to-your-room-shows-the-importance-of-privacy-defense-in-depth/
Has this been taken into consideration? -
Kind of wondering what is so hard to code/debug that is delaying the next snapshot day after day…
At this point, "check for updates" worked this morning but no longer works. The function just drifts off into dreamland, no feedback, never completes.
-
Hmm… If you look at vivaldi://voicesearch page (It's listed in vivaldi://vivaldi-urls ), you'll see that while it lists values for some of the setings, the module version information values at the bottom are reported as "undefined". Given that, it appears that the actual Google voice-listening binary module is not downloaded by Vivaldi, even though Vivaldi has this vestigial page (and as shown at the top of vivaldi://voicesearch , a few set-to-default settings values that just go unused in Vivaldi, with no voice-recognition module present to actually take them as parameters).
Compare for yourself to what you see if you go into Chrome and go to chrome://voicesearch .
-
Also, as for Chromium, from now on:
https://code.google.com/p/chromium/issues/detail?id=500922#c31
In light of this issue, we have decided to remove the hotwording component entirely from Chromium. As it is not open source, it does not belong in the open source browser.
Chromium builds from r335874 (version 45) onwards will have hotwording disabled by default and will not download the module. There is no way to enable this feature at runtime. Google Chrome users will be unaffected (although, as always, will have to opt in using settings before the hotword module will activate).
If you want a version of Chromium with hotwording, you have to build it from source, with the GYP define "enable_hotwording=1" (or equivalently, the GN arg "enable_hotwording = true"). This will produce a custom build of Chromium that downloads the proprietary hotword component.
I have also added a field in the chrome://voicesearch page (in 45 onwards) to show you whether the hotword module is installable. If that says "No", then it is not possible to opt in to hotwording (either because the language is unsupported, or because it is a Chromium build).
-
Thanks, hadn't seen that
