Snapshot 1.0.178.2 with more settings
-
There's no need to load a tab until it is clicked.
I'd say: there's no need to postpone loading a background tab if and when both of the following are true:
- The foreground tab is completely done;
- There is enough free CPU and memory.
The need for options here would be greatly reduced if we had a sane default taking the previous logic into account.
Also, more elaborate caching could enable processing background tabs much faster and with less CPU strain at a restart. This one might ask for a setting, as certain people might prefer seeing fresh content and some a snapshot of the page as it was when they left off.
-
confirmed! ArchLinux, Chinese
-
Agree, they are probably reading all this comments if they really love what they are doing and cares about client's feedback, but since monday its my 99+ visit to this page and still nothing and not a single message here or on twitter about the delay, looks like old opera manners and other big players.
-
Sorry for not posting earlier guys, but this week is pretty busy with Monday having been off (Oh boy, these are cases when non-native English speakers have to think twice… ^^) for most part of the world and most developers are not in the office right now.
As we announced in the beginning, we plan to release snapshots "roughly once a week". And we also try to be consistent with those Monday releases, but it's not always possible for whatever reason there might be.
I just had a little internal talk about it. We're going to try to calm your shaky hands down tomorrow, but it's a 50% chance only. If not, we just have to skip one and Monday will be the next snapshot. -
Well, its not that we MUST have one snapshot a week, i think its more like, in start vivaldi was developing super fast, now its kinda super slow.
I guess we all are kinda worry when we will see browser goes final, and missing snapshot gives us nothing but worries.
I think you should break rule when-its-done, and share with us more of what is currently being worked on, so far we only know you are working on everything, but what is next and progress status, we are left in the dark.
We even had survey with list of priorities we users have, but no feedback except results was presented about that.Anyway, good luck with your work.
-
Have you checked the Flags page for some of the cache and page/tab load and refresh settings you want?
Meanwhile, back at the ranch:
The Ctrl-F "Find in page" box keeps getting 'stuck' and won't close until the page is closed and reopened. I haven't been able to find the sequence of keystrokes or actions that make it 'stick'.The Bookmark editor and Notes still have problems. Bookmark text is difficult to type and Notes mangle the punctuation after the Note is saved.
Note Editor CharactersThere are a bag of flags for touch screens but only one for the mouse, auto-fill, and one for keyboard, shortcut debugging. That gives Vivaldi three input methods to use and attempt to debug when it goes pear-shaped but only a touchscreen can be configured with Flags. All of you touchscreen users go ahead and pinch the screen and fling the scroll bar now. :lol:
-
Agreed, we understand those snapshots take time to develop, and not all weeks will be consistent. If we have to wait a week or two for the next snapshot, we will gladly do so - we know they work hard to give us the best they can, we're not asking them to do the impossible. But a quick note on "sorry, this week's snapshot is coming later", or "wait until next week" is way better than no word on the matter. A quick twit would solve the issue.
-
Looks like caching is already on the way to being optimized. Now, when you open the browser in "last session," the pages are loaded from cache, saving a ton of time and bandwidth. I don't think ANY other browser, ATM, employs this efficiency.
-
Ok how do you do that?
-
When there is a delay, a short message like Christoph142's above, or even a blog post, would be sufficient to appease us. As SomiKnight implies, silence often feels unsettling.
-
Hey, we have been updating our infrastructure a bit so we had some problems. We will be back with new builds early next week… We will compensate with some new features you guys have been wanting
-
feels like vivaldi hasn't changed much for 3 weeks. Minor bug fixes here or there and none of the bugs that I regularly come across fixed
-
Nice rubshandsinanticipation
-
Win 7 64, 32 bit Vivaldi, 8 gig
~
(aka 'LAZY' tabs)
Mozilla browsers got sooooo much better after they intro'd that feature.
There's no need to load a tab until it is clicked.
~Ditto on that been thinking it would be an important feature also.
I had a remote session with a top notch tech and he cleared up a LOT on my machine, BUT Vivaldi takes ages STILL to load on SSD. Slowest of all my programs and eats up memory etc. so have to use another browser until they get those problems solved.
Like some other say can't stand listening my fan and CPU at 100%.
I'm really anxious for a "beta" maybe next week cause no update this week, MUST BE SOMETHING BIG, or a wild company party!
-
this is where rss feeder or twitter comes in handy. You don't need to visit a website everyday and refresh every hour just to see if a page been updated or not. It will tell you
-
can anyone tell me what's so special about the beta state of Vivaldi that almost everyone is talking about "beta, beta, beta"? thanks.
Because I think that it just mean that if there is no "beta 2" we will not see new features before final version and just/"only" stabilization. And I can't live with that in mind that almost everyone here wants Vivaldi to be feature complete that early and release a final (or beta for stabilization).
Not saying that Vivaldi is not usable yet but when compared Vivaldi still has nothing to say "I'm here, I'm new, I have these 10 great features all other browsers miss". for releasing a final version to get new people.
-
Waiting for email :roll:
-
Don't worry, there will be multiple betas and it doesn't mean feature complete here. It mainly serves stabilization and performance tweaks, but not exclusively.
-
We haven´t decided if we are doing multiple betas or not, but nothing has been ruled out. Features will come in more than one version anyways.
-
"I'm here, I'm new, I have these 10 great features all other browsers miss".
Plus the existing functionality of the (IMO) top Browser Firefox, mostly because of their Extensions. This is what will make or break Vivaldi. Simple, make a substantially better "mouse trap" and the users will come. If they cannot accomplish this, then they may as well abandon the Project now. Key word "substantially".