Vivaldi 1.15 RC 1 – Vivaldi Browser snapshot 1.15.1147.29
-
When maximized once, Vivaldi will open next time maximized, regardless whether or not it was actually maximized when closed. This happens since several versions of the snapshot for Linux under Gnome 3.2x.
-
@jl-frankfurt: ps. Workaround. Open the settings tab and close it makes Vivaldi start next time as expected, i.e., with the window sized as when closed..
-
Am I correct that thinking even though the Cr66 fixes are included, the user agent will ship specifying Cr65?
-
Here is mine:
Vivaldi 1.15.1147.29 (Official Build) snapshot (64-bit)User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.183 Safari/537.36 Vivaldi/1.96.1147.29
-
@rsaeks: Yes, it's a prio 1 issue meaning it's a release blocker
-
@gwen-dragon That's what I was thinking. My main concern is if the UA doesn't get updated this might result in more messages asking users to update their browser. I guess that can't be helped though.
-
Will 1.15 include sync?
-
It feels like this is back (sometimes, so maybe something else like it):
[Regression] Enter does not work on Address Bar when Address Auto-Complete is disabled (VB-34967) -
@saudiqbal: 1.14 stable do include sync which is to see as a test function. You can open it in vivaldi://experiments setting page.
-
Anyone else noticing that despite Sync working, the icon doesn't show in the tab bar?
Latest 32-bit Vivaldi snapshot on Windows 10 (64-bit).
-
@gort The icon only shows in the tab bar if you have tabs open on a window on a different profile. If you don't use that profile for a few weeks (not sure of the exact time), the tabs get hidden and the icon goes away.
-
@rtransformation said in Vivaldi 1.15 RC 1 – Vivaldi Browser snapshot 1.15.1147.29:
@saudiqbal: 1.14 stable do include sync which is to see as a test function. You can open it in vivaldi://experiments setting page.
I know I only use snapshots, I am just asking will the final version 1.15 include the sync or not?
-
External links still close Vivaldi every time.
-
@lonm: Ah, thanks for the explanation. I've just confirmed it to be the case by going to my Linux installation and checking, where the icon turned up, then going back to Windows, where it also reappeared.
I hadn't used Vivaldi on my Linux partition since 3rd April, so 17 days or less seems to be the cut-off point for the icon.
Cheers again.
-
@yamiryuuzero: Yep,very frustrated at the same time.
-
I highly recommend fixing the issue with Strict Site Isolation (VB-39198) since it effects embedded YouTube videos, certain form fields on some websites, etc. So many of us turned on Strict Site Isolation at Google's recommendation that you'll more than likely have a slew of complaints if that feature is not working as it did in Vivaldi 1.14 (to clarify, this feature is not broken in third-party builds of Chromium 65 like it is in Vivaldi, and this is more than likely a Vivaldi-specific bug).
-
@gt500 Vivaldi, with the available resources, is unable to repair this experimental feature of Chromium. Rather, Chromium is already fixing it internally, and as those fixes flow downstream, we will benefit from them. If Vivaldi DID have the personnel and time to employ their own fixes, they would almost immediately have to roll them back, as being incompatible with the new Chromium releases. If a user is uncomfortable with the Known Issues connected with this experiment, they should refrain from using it until it is ready for prime time in Vivaldi. As mentioned elsewhere, Chrome has some patches for this which make it work better there, but which patches are not available to Vivaldi.
-
@ayespy: Are you seriously going to try blaming it on Google again, when I've already verified that it is not broken in third-party builds of Chromium's source code?
Also, as I have mentioned time and time again, Google recommended turning this feature on to help prevent exploitation of certain CPU side channel vulnerabilities. Many security experts passed on that recommendation, as did at least some news sources. When Vivaldi 1.15 releases, people who followed that recommendation aren't going to understand why so many things are suddenly completely broken in Vivaldi, they're just going to complain or switch back to another browser (since, as I keep saying, Vivaldi 1.15 is the only browser I have tested that has this issue).
I'm simply trying to warn you that this bug could have more serious repercussions for Vivaldi's public perception than you might think. If you want to ignore that warning, then that's fine, however I ask that you please stop trying to deflect the issue and blame it on Google. The evidence I have available shows that this is a bug in Vivaldi, and not in the Chromium source code.
-
@gt500 you are talking to Ayespy as he was a Vivaldi coder or he can do anything about it, are you aware he's only a moderator in here?
-
@lonm: Updating it would be misleading as only security fixes got backported. It still is 65 feature-wise.