Vivaldi 1.9 – Plant trees as you browse

Ayespy

@aach1: The Team will not publish a (even short term) road map, because it's impossible to know what curves Chromium will throw at them from one version to the next, actual programming times cannot be predicted, and as soon as they promise something they find they can't deliver by this or that deadline, molten lava will doubtless flow from the forums into the Vivaldi servers. Better to surprise everyone.

xxvixxy

Wondering if at some point keybinding for Extensions will work? That or perhaps I am not doing this right.

If I am, somebody let me know! =3

Dantesoft

I wonder why Vivaldi is introducing this

I’m sure their founder made a very convincing case to Jon, but a German accent and green eyes probably helped.

I'm not saying the search engine is a scam, but I think the claims of saving the forests of the world are exaggerated, and can't be accounted for easily.

They try to account their activities but I’m not 100% sold either.

Did Ecosia contact you? What are you getting out of the deal Vivaldi, other than the warm feeling that you are part of the solution now

Weed?

Dantesoft

@gaelle said:

the restore tip didn't work for you?

“Restore” is a bit of an understatement, it misleadingly suggests you get back some settings, but don’t lose any; it actually does a “factory-reset”, so like others have mentioned, it deletes all your other custom searches.

Friends don’t erase friends’ data, so I’m not sure why you and Jon recommend that, and why the release wasn’ț postponed until Ecosia could just be added to the list, for users that customized their searches (the 1 percent?).

aach1

@Ayespy I understand not wanting to commit to a bunch of changes that turn out not to be possible because of circumstances beyond the team's control. But no-one would criticize you for saying "thanks for all the feedback. here's the list of things we'll work on for version 2.0, and don't expect that they'll all get done, because circumstances can change". I'm suggesting that after all the gathering of feedback, it would be good to let users know what plans all that feedback resulted in. And if it was possible to show how Chromium changes resulted in changes of plan, so much the more transparent.

GoustiFruit

Has this already been reported ?
When doing some mouse gestures that switches to another tab, if that tab is a Speed Dial page, then the Speed Dial contextual menu pops up.

Happens for example with:

"Close tab" mouse shortcut -> if the newly focused tab is Speed Dial
"Switch to previous tab" or "Switch to next tab" shortcut -> if the starting tab is a Speed Dial

Ayespy

@aach1: It's a bit more complicated than that. The development process is quite organic and not at all top-down or command-driven. There are meetings a couple of time a year when Jon and the entire team get together, evaluate the current state of the browser, reflect on market positions, and evolve a vision for, roughly the next six months (I think) - "where we'd like to be" so to speak, plus, "These are things we've always planned to do. Are they still wanted, realistic, practical? Should we re-order priority on some of them?" Everyone backstage can see the results of these meetings, the preferences and goals expressed and endorsed by everyone at the meeting, etc. Jon is responsible for the overall vision, and the staff imagines a path to get there. But AT NO POINT are timelines expressed or adopted, specific formats or procedures dictated, or anything like that. Just "These are the things we'd like to work on." Then real life hits - and code begins to be written and bugs squashed. At the same time, decisions are made to change direction on some element pretty much every week. Things are tried, tested, and discarded, because they seemed like a great idea but simply aren't going to do what was wanted

Yesterday, before the rollout of 1.9 final, I read a list of the things the devs had addressed in the hope of having completely sorted for inclusion in 1.9, but due to the necessity of keeping up with the Chromium release schedule (for security reasons among others, such as simply not falling technically behind the state of the Web as driven by Chrome development), had to set aside for the next Snapshots and Final, because of unexpected regressions, curves thrown by Chromium releases, fixing A breaks B, C works perfectly but introduces a security concern so has to be completely re-factored before release, etc., etc. It was an impressive list. Unless one reads it, one doesn't even KNOW everything they are trying to do.

This small team usually kills between fifteen and fifty bugs A DAY. Still, stuff they wanted in simply couldn't get in to this build. And it wasn't just one or two items. I mean these guys are building the Empire State Building, and have only reached the 15th floor so far, so their goals are extremely ambitious. But the foundation keeps shifting, storms hit out of the clear blue sky, building materials are being continually updated and re-factored, etc. So to say "we are adding another complete floor by the time the next build comes out" would be sheer folly.

They're not going to do it.

An_dz

@rseiler: A regression is something that used to work and now doesn't. This never worked in the first place.

Fixing a regression is easier because it used to work and you just need to check what has broken it.

Fixing something that never worked is harder as you need to figure out what to change.

An_dz

@goustifruit: Yes

Mauley

I came from Chrome to Maxthon and then to Vivaldi. Now I am using it for over 1 year. I love every update because it always improves something visible / functionally as well.

Greetings from Germany
-Dennis
Owner of 144Hz Monior.de

finneko

Is last snapshot 1.9.818.40 same as this stable 1.9.818.44?
I ask because Help/Check for updates... does not update 1.9.818.40 to 1.9.818.44

Ayespy

@finneko: It's essentially the same. Snapshots do not update to Stables, and Stables do not update to snapshots.

finneko

@ayespy: That's what I thought, but I wanted to make sure. Thank you!

iAN CooG

confirmed fixed in 1.10.829.3
that was fast

hub965

Хотел, чтобы закладки сортировались по алфавиту. I wanted to sort the bookmarks alphabeticallynull

hub965

Когда будет синхронизация личных данных?! When will the synchronization of personal data?!

xstrike999

I just updated but I am still unable to move around or re-position the extensions!

ghpy

@xyzzy:
It probably always depends on what one considers "high". Starting Vivaldi and only opening this page makes Vivaldi consume about 1 GB of RAM on my Debian system. Every additonal tab (no videos, just text and a few pictures) adds about 300 MB. I think that is high considering the task.
Vivaldi's CPU usage does not seem high to me.

xyzzy

@ghpy On my Mac, each helper/renderer is currently using between 115MB and 200MB of virtual memory according to Vivaldi's task manager. (These are for "typical" web pages; text with some pictures.) Physical memory usage, according to the macOS Activity Monitor, is considerably less.

I'm using uBlock0 and have done a few tweaks via Settings/Preferences to disable a few Vivaldi features that I don't need but haven't done anything extreme to minimize memory usage.

rseiler

@An_dz said in Vivaldi 1.9 – Plant trees as you browse:

@rseiler: A regression is something that used to work and now doesn't. This never worked in the first place.

Fixing a regression is easier because it used to work and you just need to check what has broken it.

Fixing something that never worked is harder as you need to figure out what to change.

Never worked? The whole time I used Vivaldi as a regular browser, since late last year, it worked. There was a clear difference in behavior after 1.7. Some people did mention that they first saw a problem a long time ago, but that they only rarely saw it since then, if at all.

The tab-stack variation that I mentioned in detail, which doesn't even involve tab cycling per se but clearly must be related to it given the context of the issue, was brand-new behavior to me and highly noticeable in 1.8 once I figured out what was going on. I could go back to 1.7 right now and use it all day long and never see it, yet it always happens in 1.8/1.9.

That would seem a regression.