Snapshot 1.0.435.22 - Bugfixes and Breakfast
-
I would like to have close tab and go to right before final.
To me closing a tab is still one of the most awkward things about Vivaldi.
-
The one issue I've had with Vivaldi lately is that often pages don't load completely. Basically it seems like the connection timed out, and the page loads with images missing, or some CSS not applied or something.
I've noticed this after switching to Windows 10. I also bought new hardware at the time. So it could be an issue at my end. But I think it was around Beta 3 when I got the new hardware set up. I haven't tested in other browsers.
Has anyone else had a similar issues?
-
You can see (almost) the whole team on https://vivaldi.com/team/
-
The difference with the others OSes is that Linux is so advanced, that the parameters of the languages can be handled directly on the OS level. And Vivaldi is nicely integrated in that way.
But I agree that an option should be provided, and there will be. A discussion about that happened recently. But I don't think that will happen for the final.
In the mean time, you can use the command line with something like "LANG=en_US.utf8" (I don't remember how to do it exactly, but you get the idea). -
It would be nice if you polish the UI before stable release:
-The window controls are black with color area behind tabs on windows 10, when they should be white. imgur.com/XnA5lul
-White stacked tabs are not really visible with color area behind tabs and with tab spacing remove in maximized windows. http://imgur.com/a/gdvMd
-
I totally agree with both of you. The history page is ugly, so are some options pages, and really, any remnant of Chrom*.
But building a browser is a long and hard task. Each of the Chrom* functions have to be recreated from scratch. That's why they prioritized and choose what to rewrite first, while keeping other parts of Chrom* intact for now. In that way we can have a great browser that can do almost every thing, even if part of the UI is ugly, instead of an half browser that have a perfect UI. I think it's a wise choice.But of course, all that Chrom* part will go in the garbage sooner or later. My personnal priorities are the history page and the badge.
-
Just so you know, it was FB fault that Vivaldi had to fix. Bad FB, bad !
-
I have no idea when M3 will be released either. The motto of Vivaldi is always "When it's ready"
But be assured that as soon as they are confident there can't be any loss of data, they will add it in the snapshots
-
Yes there is an issue that Vivaldi is stealing the focus. It should get fixed shortly.
-
Bookmarks AND separators = good. O12 bookmarks = good. Please make bookmarks much like O12.
-
You can see (almost) the whole team on https://vivaldi.com/team/
Thanks for that Cqoicebordel! 6 out of 33 if I counted right! Not too bad I suppose…
Cheers, Harry -
Single-key shortcuts don't work with the numeric keypad.
And please add the "Insert note" option.
-
If you are not using more than 4 GB of ram with your browser, there is little benefit running the x64 version.
Actually, the x64 on its own will already use more RAM with the same tabs as the 32 bit. This is why most browsers and softwares today default to 32 bit.
As for Vivaldi, I think they test the 32 bit as stable and consider the 64 bit as experimental since it will just not receive the same love and testing in general.
-
1. When starting up, random older items in history show up in tabs rather than the tabs that were open in the last session.
2. X-notifer extension worked fine until some 4 or 5 snapshots ago, and has never recovered to work properly since then.
3. Occasionally, a "hidden" tab must be closed. "Hidden" meaning the URL shows in the address bar, but there is no tab displayed for that URL. I still have to close it via Ctrl-W.
Vivaldi is pretty nice, but still seems a bit shaky to consider for a Final, in my opinion. Chrome extensions don't play so well with Vivaldi as they do in other Chromium browsers, from my experience (#2 above is just one example).
I still miss turbo-bookmarks via F2 that Vivaldi once had, also.
I am seeing too many regressions in recent snapshots, honestly.
I am on Windows 7 (Starter) OS, 32-bit.
-
Sadly web panels remain broken, as many in the community have also pointed out in the last few SS's. No web panel will reload when its home button is clicked.
They are working fine for me on Linux (Manjaro/KDE)
-
The Chrome extension "Google Translate"(https://chrome.google.com/webstore/detail/google-translate/aapbdbdomjkkjkaonfhkkikfgjllcleb?utm_source=chrome-app-launcher-info-dialog) it does not work. Twice it worked and then it was over.
I use this for a long time.
-
I gave up on the web panels a few snapshots ago … just open the webpage in a tab now ... another regression, yes.
-
I'm using Linux Mint Cinnamon x64 but the only keys that work are '*', '-' and '+'.
'6', '7', '8' and '9' aren't working, I have to use the alphanumeric keys.
I think is not related to my system, these shortcuts are working in my old Opera 12.16. :oops:
-
Hm, those buttons work with my Logitech in Win, but I can remember that a longer time ago there was a problem with one of the Logitech mice in combination with Linux - maybe some more info is needed (Model, OS to which it is connected, etc. pp.)
-
About the old thing with the 4GB:
Each tab gets its own process - unless forced not to do so by some esoteric flags, which is really not recommended - and if one single page in a tab exceeds the address limits imposed by 32bit, there is something wrong with that page.In terms of security the 64bit version might even have an edge over the 32bit version - at least if the relevant parts are similar enough to the stuff Chrome uses, but of course Vivaldi is not Chrome, even parts of the core are different, so the following article might not apply to 100%: http://www.howtogeek.com/241501/you-should-upgrade-to-64-bit-chrome.-its-more-secure-stable-and-speedy/
