Stabilization starts for 2.5 – Vivaldi Browser snapshot 1525.30
iAN CooG last edited by
@Gwen-Dragon yes I did, and different times over the years because it's one of the many things constantly geting fixed and broken again over the releases. It's even getting boring reporting the same issues over time, but I can resend some reports, I should have them in the sent mail folder
TLGreg last edited by
@archive1 Next restart or even next window opened will have pageAction duplicates again.
Hopefully, this will mean support for
chrome.pageAction(I couldn't see any of those for a while in vivaldi).
But yeah, duplicates of buttons that 24 extension puts up there is not really great.
"save as"is not working here, in my case I tried with image I do not know if it proceeds to other files.
iAN CooG last edited by
Summary: Search field bugs
Summary: Address field dropdown bugs
it was almost the same report as
Summary: Address bar history dropdown and Search bar history dropdown don't react on Shift-del; Mouse over on "X" doesn't move highlight
and while at it I did also this
Summary: Save link as/Save image as always save to default dir
Bug report follow-up.....see https://forum.vivaldi.net/post/288497
VB-52492 Deleted bookmarks return only on installs with default status possible.
Stable install and one Standalone see the return of the deleted bookmarks.
One standalone does not. This one cannot have default browser status.
If this is in the wrong place please move it. But it is related to the release of snapshots. Directly related.
it got released to us Snapshot testers so that we can catch bugs like this before they appear in Stable releases
I've been here since the start, so i have at least some understanding of how it works. I've always been an ardent fan of V, & remain so. That does not however disqualify one from offering constructive criticism on occasion, & IMO this current SS is one. Is there not a stage pre-SS, wherein the Sopranos get, see & use the candidate? All it would/should have needed was a single Soprano [who uses Extensions] to fire up this candidate, & BANG the new unprecedented bug would have whacked them in the face, which could have instantly been fed back to the Devs for restitution... & then proceed again.
@Steffie You make a very valid point. FYI, Sopranos are not usually involved in testing the actual Snapshot builds prior to release. We do 99% of our testing with daily internal builds. That covers testing of new features, Chromium updates, etc. and we, along with Vivaldi's QA team, do the best that we can to ensure that the worst of the bugs (and really weird, subtle bugs that might slip through automated testing) are identified and fixed before Snapshots get released.
Sopranos also are not usually involved in testing Release Candidates, Stable builds, or mid-cycle Stable updates in advance... unless some item in the changelog requires extra testing.
@xyzzy Ever since my preceding post i've felt bad, that my poor wording might have seemed like i was attacking our Sopranos. I did not mean it to be so, nor to sound so.
Instead i'm simply thrashing about here in puzzlement about how it came to be that this SS, unlike so many before it, contained such a staggeringly obvious new bug, which would/should have been exceptionally easy to spot, had
someoneonly launched this "SS candidate" prior to releasing it as a formal SS. As an aside, the irony was almost laugh-out-loud funny that such a blatant unsubtle new bug should arise in a version touted as "Stabilization starts...".
Though the point i'm struggling to make, & which i think Ian has been making, seems to be being comprehensively misunderstood or otherwise vociferously disagreed-with by many here from whom i'd have expected different, i continue to opine that this Extensions bug is of a fundamentally different nature to the majority we SS users have historically seen. By that i mean that many prior bugs might afflict one OS-branch only, or only a subset of users who happen to perform Thing1 after Thing2 after Thing3, or only some users who use a particular combo of Settings, etc... ie, bugs not necessarily universal, & not instantly in your face the moment V-SS launches, without actually needing to first "do" anything to force the bug to manifest.
Put another way, many historical bugs have a degree of subtlety & "hiddenness" about them, such that the SS-user community is ideally placed to discover & report them. This Extensions one however is so unambiguously "unhidden", so obvious, so blatant, that surely it's not so terribly unreasonable to suggest it could & should never have escaped out the door?
@Steffie No worries. I understand and appreciate the frustration that's been expressed here. I also didn't take any of the comments from you (or anybody else) as attacking the Soprano team in any way. I was just sharing some insights into the testing process and pointing out what makes release candidates a bit different from other Snapshot builds.
i_ri last edited by
blatant unsubtle testing process insight is a good reminder of things like this. test buttons in new position. without regard for anything else. like them being still in the old position. thoughtful procedure is not a bug sometimes.
@Steffie For what it's worth, developers mostly run, especially for QA, "virgin" installs of Vivaldi. That means no extensions are installed. In my case, as well, I studiously avoid running any extensions. At all. Ever.
I do run a single extension, and have done so for years, that being one to make it possible to copy text without formatting. On none of my installed instances does it show an icon.
All that said, the extensions icons regression is cosmetic, though a "disaster" for those who use numerous extensions, and it will obviously be addressed before release to Stable. These things happen if you're a Beta tester, but you roll with the punches, and within a week the "disaster" is remedied.
But I thought it might be helpful to bring up the fact that there is a reason why extension bugs are, pretty much always, invisible to developers. I will also note that SIX MINUTES after the snapshot was released, a Soprano filed a bug about the extension icons in the address bar. Six minutes. And with three exclamation points, to boot. I think the devs will be on it pretty quick.
In my case, as well, I studiously avoid running any extensions. At all. Ever.
Well do i know & remember that. I trust that you were able to clearly read between the lines when i not-so-cryptically stated
needed was a single Soprano [who uses Extensions] to fire up this candidate.
Dystasia last edited by
How can I move all my settings to the stable version from the snapshot version. I thought about it and I will not be using snapshots as my daily driver anymore. This isn't the first time something so obvious completely evaded all internal qa/testing layers (not even going to mention all the bugs that come back every couple of snapshots). I'm scared for my data now.
@Ayespy I do have one extension installed, but I only noticed the bug after I read some of the posts in this thread.
People get way too excited about non-critical bugs. This one might look ugly, but it not much more than a cosmetic issue; a minor loss of convenience at the most.
Dystasia last edited by
@pesala: Thank you so much.
QuHno last edited by
@Steffie We didn't get this snapshot before you have got it and I didn't have the problems before I restarted the browser after the initial restart on install, basically 10 minutes after someone reported it here and I tried to reproduce it.
The last snapshot we've got from this series was 2.5.1525.9
After that some fixes were cherry picked and probably one was faulty, at least for this branch.
Several of the errors are not in the internal version, which is from a different branch, but there are others ...
@Steffie This is true, but in no case does a Soprano test a version prior to release. We (and you) all get it at the same time. QA runs some 600,000 automated tests and several in-person tests, but hey - not everything can be tested, especially with virgin builds. And they do have to be tested virgin, because that's the only way to weed out variables. When the devs get a regression report like this one, they test the crap out of it before the next Snapshot release. But that's why anyone and everyone can download and run a snapshot.
TerDale last edited by
@archive1: great tip, thx!
TerDale last edited by
@archive1: oops, wasn't aware that issue will be back upon next restart...