Feedback for Weekly build 1.0.94.2
-
Speed-Dial Frontpage: Still loosing preview pictures, after a new start of Vivaldi. Only after first actions all previews are back again.
»V« Logo with the menue and then to »settings«: This box is now out of Vivaldi since the second alpha. It starts slower and doen’t look as it belongs to the browser, even with a different style. The first version (also attached to the »V«-Menue) fits much more.
… even the size of the browser windows is missing after a new start of Windows. It will only be half of the display.
-
Han.
It's time to test the new snapshot.
-
Maybe not clear?
When I click uninstalled vivaldi to install a new version of vivaldi, I came across an option which say "Delete your browsing data" It actually deleted my bookmarks as well. I wasn't aware browsing data also meant bookmarks, I thought it meant cookies, history
-
Maybe not clear?
When I click uninstalled vivaldi to install a new version of vivaldi, I came across an option which say "Delete your browsing data" It actually deleted my bookmarks as well. I wasn't aware browsing data also meant bookmarks, I thought it meant cookies, history
There isn't any need to uninstall the old version.
If you have some problems can be useful to delete the data directory of the current user, but usually is not needed.
As happen with most of the multiplatform programs that uses a data folder and not the windows registry to store the personal/configuration data (opera, opium, firefox, vivaldi and so on…) .
-
Similar issue with the tabs except focusing on the "covered" tab still reveals no x to close it. I have to close the tab in front of it or move the covered tab to the far right to expose the X and then you get the + for the new tab in the middle. No prior installation.Windows 8.1.
Attachments:
-
Please, make it clearer on the forum threads the Vivaldi Browser for (platform) is the thread to go for feedback on the browser. A lot of users believe the Bugs - The Official Bug Thread and TOPIC: FEATURE REQUESTS are for the browser rather than the forum! Simply name it Feedback for Vivaldi Browser (platform) and the confusion should be cleared. Also, I wouldn't have known about the updates if a user hadn't posted a direct link to this thread, so you guys really should work on that.
Of course, I still believe the best option would be a blog like Opera's, where news are made clear, and don't require browsing for that one specific thread you want - it's the only thing Opera does better than Vivaldi now.
Thanks to that confusion, a lot of my feedback got buried under threads that are not related to the subject they are about, and so have done a lot of other users. Check those threads, move the posts to where they should be, and find a way to make those updates news more accessible to the userbase (again, I believe a blog rather than a forum is the best tool for this).
But regarding this update, I have no more problems staying logged in, even after opening a new tab, and Youtube runs 1080p@60fps without any problems! Nicely done!
Edit: I thought the issues with Youtube were gone, but they are not. A video rendered in 1080p is still running only at 360p on Vivaldi, even though other browsers run at max resolution.
-
@Gwen-Dragon:
@moderator
Please close this useless old version thread.
It misleads users for posting bugs and feedback of current weekly.Are you saying this isn't the place for talking about bugs and features either? If you read my post above you'll see I've had problems with where to post about that, and another user sent a link to this page, but is it not here either?
-
What I'd personally like to see is a separate, pinned thread for each Vivaldi version in existence, at least until a version is "officially" deprecated. Since nobody is currently being forced to update versions, that would involve a thread for each version to date. It might be useful to have those thread titles reflect each version along the lines of that existing thread having a good, clear title: "Feedback for Weekly build 1.x.xx.x". That way, a user could submit a comment into whichever version thread corresponds to the version he's using. If a version is considered by Vivaldi to be deprecated, then that version thread could be locked and unpinned, with a final post that the version is considered obsolete and should be updated.
-
What I'd personally like to see is a separate, pinned thread for each Vivaldi version in existence, at least until a version is "officially" deprecated.
Come on! What's the point of using an alpha version of something when two other (newer) alpha are already out ?
I can understand an user who use the version 1.x.y instead of a 2.0 beta 1, that could be a wise decision, but now we will see just major improvements (maybe with minor regressions) for a reasonable number of weeks.
Then we could talk about conservative or aggressive upgrade paths.
-
What I'd personally like to see is a separate, pinned thread for each Vivaldi version in existence, at least until a version is "officially" deprecated.
Come on! What's the point of using an alpha version of something when two other (newer) alpha are already out ?…
I'm merely considering the confusing situation during the several-day overlap when users with one version have problems and come here to post, not realizing until they have already done so that there's even another version issued. Part of the problem right now is that you can come to this page directly (as many do) and have no idea your version is out of date… hence you can (and some do) post in some current-version thread about a problem in an older version. This is what is happening now, and adds to confusion. As I explained earlier, deprecation via thread-locking of the bug-thread and its sinking/unpinning would act to clear out the truly older version bug-threads quite rapidly, at Vivaldi's discretion.
-