@Gwen-Dragon I don't believe it is a bug!
As users we have a choice, let the setting be controlled by the Browser OR by Extension(s).
If we want an extension to control the setting, then the browser handling should be turned off (in this case Enabled).
If we want the browser to control it, then the extension handling should be turned off.
@RichardDick said in Vivaldi gets stuck/repeating Cloudflare's "Checking your browser before accessing" DDoS prevention page:
@jubuttib I experience this issue in every browser (not just with Vivaldi) on some websites that use CloudFlare. So I can assure you this is probably an issue on CloudFlare or the website's end.
Interesting, when it happens does it happen on all browsers, or just one like it does on my end? And yeah I'm sure the specific website/Cloudflare implementation has an effect, would be interesting to figure out what it is though and see if it can be worked around.
Same issue here. Whenever I have to downolad something I usually have to open whatever I'm using (telegram, whatsapp, messenger, trello...) on a normal guide and donwload it from there. But it's just bad user experience.
On opera I'm able to download normally from the side pannel.
May be your browsers have different File Type Policies databases. These database are used to protect users from malware. I guess this is part of Safe Browsing feature (Phishing and malware protection) in Vivaldi.
See internal page vivaldi://components which version you have.
I have: File Type Policies - Version: 42
Yers. The issue is still present for Amazon.com... pages freeze, stuttery scrolling, or very long load times when either scrolling or attempting to access another page. Whereas no issues with Firefox, Opera, Chrome, Edge.
There's no need for a stopwatch. When there is a perceived performance issue, the browser offers profiling tools built-in that will measure performance, as well as help diagnose the issue. If people seem to be experiencing performance problems, then the best thing to do would be to profile it.
This is primary way to get an objective measure of performance, and also diagnose performance problems. It can surprise you as well. I can't count the number of times I've seen someone report a perceived performance issue, and point to another product or configuration that supposedly performed better, only to discover the opposite was true after they were profiled.
On the net, I've seen this lead to flaming responses as someone just digs in and defends their their claims, disregarding the evidence, and ending in personal attacks. But in collaborative teams developing software together, it's an invaluable tool.
So if you're experiencing persistent performance problems, especially ones that others are having trouble reproducing, it's likely worth your while to learn how to use the dev tools to measure performance and diagnose issues. If just a few people are having problems while most aren't, then in the absence of other relevant information, I'd venture to guess there's some configuration or extension as the root cause. Which could probably be tracked down using these tools.
Here's a link to Google's getting started guide. There might be a more recent page on the topic, I just grabbed this quickly from a web search. So I'm not vouching for it as the best starter guide, just helping those who may be interested jump start their research.