I have a similar problem. Please see the attached screenshot, notice the right hand side. Thinkpad X1, Windows 10, 64bit, high resolution screen, latest vivaldi stable version. I tried all sorts of settings. I currently set the ui scale to 95%, but have also tried to set it back to 100%. Doesn't work.
Sorry for the intrusion on the thread. I also have the same issue, and I don't have any of the extensions as mrlenxa does, and I didn't set any flags. To me, it also happens after Vivaldi was in use for a while (at least 2 hours). This could be a sign of resource leak.
I identified that the problem is with Ublock Origin using custom dynamic blocking. I have no idea why issue persists even with turning the add-on off for the chrome web store. But it seems that it is not Vivaldi's fault. Thank you for your help.
@stpvid1 said in Can't watch Amazon Prime:
@rafiki said in Can't watch Amazon Prime:
Annoying, isn't it, to have to leave one browser to go to another for an, apparently, simple service which they can all do except for good old Vivaldi!
I contacted Amazon thru their Chat help service and told them about Vivaldi not being able to play Amazon Prime movies or previews. That it cuts out after 10 seconds with an error.
They said it would be forwarded to their Tech Team to be aware of the problem to look into it. So maybe they might be able to have it as an approved browser on their site.
As of now I use Firefox60 to watch Amazon Prime Videos, maybe Vivaldi will be allowed if its their servers causing the problem.
Good idea! I have just contacted Amazon Spain on Chat and they will also pass on the problem to the technical department.
@pesala said in Interacting with Reddit embedded videos causes Vivaldi to completely freeze:
@terere said in Interacting with Reddit embedded videos causes Vivaldi to completely freeze:
I hope this makes it to stable eventually
Sure it will, but the next stable may be months away yet. If it bugs you, install the Snapshot as a standalone version.
It seems they included this fix in the latest stable patch. At least from reading the change log.
Having tried it, I feel like this is the intended behaviour. History is designed to keep track of the sites you visit, and there's no need to track a site more than once. - Think of <a> links that get coloured purple after you visit them once - a link being visited once is all a browser realistically needs to remember to render the web properly.
However, thinking about it, it does seem odd that the entires jump about when the history view is designed to look like a calendar. In that case, it seems like you would want a log of sites visited according to day:
The reason it was implemented with a calendar view was, in part, to make it easier to find sites. Say you couldn't remember a particular site, but knew you visited it on a certain day. This use case would be broken if you had accessed this site on a later date but forgot about it.
I tried some other browsers to see what they do, and both edge and firefox only seem to keep a single entry per site with the date being the latest visit.
Edge wins some points as the "old" history entry lingers for a little while, but it wouldn't surprise me if that was a bug.