Vivaldi 1.5RC 4 - Vivaldi Browser snapshot 1.5.658.42
-
In our fourth 1.5 release candidate we resolve an issue with Netflix on macOS and fix a crash when using Chrome Apps.
-
W00t? #1
-
Thanks!
-
Hi Guys!
since the versions are called RC, the search-box-keyboard-bug is back.
Lost the Ticket-ID but easy to reproduce.- Insert some text into the search box
- Press "down" to open the list of available search engines
- Select one by keyboard
- Press enter
Result: The search is performed by the previous engine and the chosen one is selected afterwards.
Desired: Use the search engine the user chose.
But except for this, great work!
eini
-
I just updated (automatic) and when Vivaldi restarted all my tabs showed data from November 7 :!:
How is that possible :?:Win7x64 Vx32
EDIT:
I am using a startup parameter –disk-cache-dir="T:\Temp\Vivaldi".
I wonder if Vivaldi does not care about this when it restarts after an update and reads data from some other folder(s) ...? -
No issues to report with the macOS build. I can also confirm that Netflix works again, and with a clean install/fresh profile.
You all did an amazing job with this release. Congratulations!
-
Chromium… You can read more about it in the v 1.5 RC2 blogpost (search for my nickname there or gaelle's one)
Will be fixed probably until next release (1.6 or 2.0), not for the 1.5 since it's a bit more complicated. -
Yep, I've read your post in the 1.5rc2 blog entry, thanks for the clarification.
I understand that it can be a lot of work, especially for translators which are often volunteers… However, like Rossman, I think that these 4 strings "Open link in" are extremely important because users see them after every single right click on a link, which is one of the most common action. It really gives a bad perception to a new user for a final version, because it "seems" to be something very easy to fix, and gives the false impression that they don't care about it. Vivaldi is in a phase where it is trying to catch new users, and impress them: feelings are important.
I am not aware of the internal difficulties, but i think that these 4 translations should deserve a special treatment in order to be ready for 1.5, and let the other one for 1.6, especially if the strings were already translated in a previous release (so no "translator work" needed again?).
But anyway, my request should only be seen as an "encouragement", I'm already grateful for the work of Vivaldi staff... and volunteer translators like you -
a biiiiig thank you, for the incremental update system (probably the best new feature implemented)!
-
a biiiiig thank you, for the incremental update system (probably the best new feature implemented)!
-
Confirmed
-
Confirmed on OS X as well.
On a related note, after confirming this glitch, I clicked the drop-arrow on the right – clicking on the X (to delete the item from the search history) appears to do nothing. If you then change the search engine back using the "magnifying glass" dropdown, then click the history dropdown, the search term is no longer in the list and was in fact deleted successfully.
This is probably the same bug:
- Search for something (anything) in the search box
- Click into the search box and delete the text with the backspace key
- Click on the history dropdown and (try to!) delete an item from the history
- Change the search engine and look at the history again
-
The issue is translating those 4 strings is (almost) the same work as translating all the others Chromium strings. The issue isn't the translations, the issue is using, reusing, integrating, modifying, the Chromium assets. And each release of Chromium mix up all its strings, just for fun. It's a HUGE work to track all of those.
Be sure it will be done, the devs and the translators are clearly not happy about the current situation. It's just taking time -
Many thanks for fixing the apps launcher crash VB-22908!
Well I am happy to finally say that at long last I'm ready to make Vivaldi my default browser. I've been with you guys since the first alpha previews and I've itching to ditch Firefox since way before that.
Now once 1.5 releases switch browsers, and I'll also be installing it on my family members computers immediately \o/
-
Warm restart with one tab and one stack of seven tabs is about five seconds. Plenty good enough for me.
One glitch I noticed is that the context menu on a tab stack says "Move Tab" and not "Move Tab Stack." The result is that the entire stack of tabs is moved to a new window, so the wording is wrong.
(VB-23395) Incorrect Context Menu for Tab-stack Move To Submenu
-
Olli doesn't work at Vivaldi since a while ago
-
I have reinstalled my Windows. Which version should I use? 32bit or 64bit?
-
32-bit is recommended.
-
Why 32-bit is recommended? Also for windows 10 64bit systems? Can I change to 32bit without loosing my preferences, passwords etc.?
-
Rossmann wrote about the missing German translations into offer like Open link in new tab, background tab …., Open Image in New Tab ... etc. No website.