Snapshot 1.0.420.4 - Search suggestions and further bug fixing
-
Yes, "Is it the engine or the wrapper?" It makes me have to watch both streams and my eyes can't track and swivel like a chameleon's eyes. Anywho, aside from the crashing it's not too bad, at least the Extensions and their buttons display and work correctly.
If you can keep the page from crashing long enough to read it, here's an update on another famous company that built a bullet-proof shell around an engine from another comany:-
http://jalopnik.com/the-delorean-is-coming-back-thanks-to-this-new-law-1755528406
-
Windows 10
-
I'll try the x86 version but there is a little more involved than just installing it.
Even as Standalone installs the two versions don't play well together so there's some minor housekeeping that has to be done that I don't feel like doing right now, I just spotted another piece of lint on one of the dogs and it has got to go.
-
Everything is slow on my Windows 10 X64 V X64.
-
I think it may be related to the Cursor Navigation fix.
Mix a keyboard-related bug fix with a new engine and you have soda crackers instead of graham crackers.
The PageUp/PageDown, Home and End keys don't work 100% and scrolling with the mouse wheel can be somewhat erratic.
The 'W' key works fine and Shift-Arrow makes the orange highlight travel smoothly. It once again has its bad habit of doubling up Tabs when selecting a link: reopening the last seen and closed Tab along with the new desired Tab.
-
Did someone noticed the trend? Every time they upgrade the Chromium core, everything goes back to hell in terms of stability. Bugs which where fixed come back, new bugs appears and all the performance or stability fixes are suddenly gone. Then they start to fix things and make it stable again until the next Chromium update…
I'm really worried about this approach for several reasons. First, it means the Vivaldi Team could prefer not to update the Chromium core as offend to avoid issues or delay it, like Opera is doing. This means security bugs will not be implemented fast enough when they are patched in Chromium. Maybe Vivaldi relies to much on the Chromium core and they should strip it apart, in particular those parts that are causing this issues when updated. Its either that or build a heavy automation platform that tests every single feature and combination on all operating systems Vivaldi runs before release and hope it detects all issues in advance.
I'm worried about this approach because every time they update the Chromium part, everything goes back to an alpha state.
The other solution would be back porting like Red Hat does with PHP and other Linux packages. You stick to a specific Chromium version that is stable enough but patch the security holes on them only from the new versions. So while its not the newest Chromium engine, its protected against new security issues since the patches where back ported.
The problem with depending on Chrome is that you guys at Vivaldi are at their mercy when it comes to security and stability. And if you cannot patch them fast enough, Vivaldi will be a superior browser in terms of features but an insecure one as every hole that affects Chrome will probably also have a direct impact on Vivaldi. I'm really curious on how you plan to do this with the official releases once they are out because sometimes Chrome has a security patch almost every week, so if you didn't update the Chromium engine for several weeks or months, it will have very nasty security holes in it.
I know, not even version 1 was released, but you should slowly start to plan ahead how this will be done with stable releases, as you cannot expect users to report all bugs, in particular a regular user will not downgrade anything, he will notice something is not working after some update and switch browsers. You know rely on the community, but if some many users report this build is broken, it means you didn't even tested this internally before launch. (manually or in some automated way)
-
I would love to actually have an integrated RSS reader.
-
First of all, thank you for your hard work creating Vivaldi. I have a special interest in the workings of the bookmark function since I have approximately 55000 entries in my bookmarks in several folders and sub-folders. I have two issues and one function that would be really nice to have.
The first issue I have is concerning the sorting of the bookmarks. If I sort alphabetically, it sorts the folders and top-level bookmarks together and not separately like for example the windows explorer does, meaning first the folders sorted and then the bookmarks itself.The second issue is, that its currently not possible to just drag a tab into the bookmark panel to create it as a bookmark. The current way to do this is a bit too long-winded, especially concerning the high amount of folders I have.
The feature that would be nice in the final release to have is the currently disabled option of importing bookmarks from .adr (old opera bookmarks) and .html files. Also it would be nice to get an option to import the session.ini from the old Opera Versions (V12 max)
-
As you're fixing problems with youtube … twitter videos do not play as well. Twitter tells me the browser is not supported, even with useragent changer addon, so it seems to be a real video problem, not a browser detection problem.
-
The answer may be to run three streams (developer, beta and stable) like Chrome and Opera do. This keeps a stable version in use on its older version of Chromium, the next version of Chromium in bug-fix state just behind that, as Beta, and the next version of Chromium getting new features and bugfixing just behind that (as Developer). In such a case, if we had a Stable version, it would be on top of Chromium 47 and would be receiving no features, no bugfixes, and only critical security updates, Vivaldi would be working on bugfixing Beta on top of Chromium 48 (which would be released to Stable as soon as mostly bug-free), and would be bugfixing and adding features on top of Chromium 49, as Developer. The main drawback to this approach is the rather large development team it requires. Otherwise, one could always have a "stable" version resting on Chromium 48, and Chromium 49 could be being held back (released in snapshot versions only) until all of the crap that 49 broke could be fixed, and released a week or two "late" once it was at least no worse than Stable.
As you mentioned, the weakest link in the chain is the merciless and continuous moving target of Chromium releases, and the way these break multiple working functions in all browsers based on earlier versions. It's a challenge, indeed.
BUT DO NOT mistake each new Chromium version as necessarily being in ANY WAY more secure than the prior one. New versions only change the way things are done, and do not necessarily offer any more security than prior versions. FURTHER, Chromium always updates earlier version numbers going at least one or two back from the Canary level of development, to backport security fixes. Hence, ver. 48.0.263, for instance, can be replaced in Stable with, let's say, 48.0.275 with little or no impact on the functionality and stability of the Stable stream.
-
This build is working pretty well for me.
If you really want the latest and greatest a browser engine has to offer, you have to use the browser the company is offering themselves, which pretty much leaves you with Google, Microsoft and Mozilla on Windows. Derivates will always lag behind more or less.
But I guess once Vivaldi goes final there will be more update branches to choose from. Even now you can basically stick with beta 3 if you don't want to break too many things.
-
@Sajadi:
In that case, let us hope that Chromium 49 is not the same ugly mess like Chromium 48 was and that those new issues can be fixed with upcoming snapshots and are not dependent on creating a special unique fix or once again a major Chromium version update to address them. But somehow i doubt it, Chromium team seem to release quite some lackluster Chromium versions in general lately.
Each new Chromium engine version is relatively certain to create the same level of mess as each version did before it. Count on every new version to break dozens of things that were working fine in the browser which was built on the prior version. Such is the reality of relying on on a browser engine over which you have essentially no control, and whose builders never test it under your particular browser. The plus side is we are guaranteed web compatibility forever. The minus side is that if we want our own UI and our own options, we must tolerate continual disruptions from the underlying substrate.
-
Ha! Can't be deactivated, and doesn't work, either. Scrolling is exceedingly choppy in 32-bit on win 10.
-
BIG, BIG QUESTION: (for me at least) Has NPAPI support been totally and irrevocably eliminated from Chromium 49, or can Vivaldi still turn this support on at their end? I have a government website I use daily which is built in Silverlight - and if NPAPI support is gone forever, I have to use Opera 35 or find and open IE, just to use the site. What say you?
Edit: Just called the tech gurus at this government department and they are testing a Beta of a .js version of their web application in house. They hope to release it this month. So even with the permanent loss of NPAPI support, I may survive.
Volunteer Mod and tester on Windows 11 Home X64, i7-13700 @ 5.4 GHz turbo; Intel UHD 770 graphics; 1TB NV2 PCIe 4.0 NVMe SSD; 32 GB DDR4-3200 RAM. Community Code of Conduct
-
Well, why not just use the latest and secure version of Firefox which still supports NPAPI?
-
The Smooth Scrolling checkbox works for me in the Webpages setting box and in the Display All list. It's not particularly smooth but the checkbox works.
-
Uhhhmmmm, because I kind of hate it?
-
Yeah. For my purposes, I had to roll back to 1.0.418.3
Just too many little glitches for me to survive during my workday. Look forward to the next release.
-
So you would rather use an insecure browser version, just because you hate the better alternative? Ok then.
-
Yes, a regression. VB-13726. Hopefully to be fixed soon.
