Fixes for recent regressions – Vivaldi Browser snapshot 1849.7
-
@mtaki14: Yep, quick commands. My bad!
-
@ornorm: * Quick Commands. Oops
-
@MasterLeo29 What we think? Amazing idea!!!
-
@Ornorm And the use cases would be?
-
@kahukura Well, at least for me, since I use Quick Commands quite often, I would like to first create some pre saved timers like "water reminder" or "Update task board reminder" and such when I'm working. For the last one, I would use it when someone tells me / messages me with something like "dont forget to assign this task to X" or "have u already updated this week's Y" and etc, and then set the reminder for later so that I can continue focused on the current task
-
@MasterLeo29 What is wrong with the presets on the Clock? You can create your own. Select the preset then click on Start.
-
@Pesala I know that, that was not quite what I tried to explain. I would like to "access" the preset countdowns we can create on the clock with Quick Commands.
Edit : Essentially, just be able to launch the quick commands and type something like "Start <preset_timer_name_here>' -
@kahukura Easier access to it (access by keyboard instead of mouse). @MasterLeo29's explanation makes sense to me.
Might also be interesting to have them in the Keyboard shortcut list. -
@Ornorm I can see that working. One shortcut to launch the clock's UI, for people who dont like too many icons up front. Well... We should create a feature request, seems to be the next step
-
@Ornorm This sounds like creeping sophistication to me. The clock is just a utility.
-
@Pesala I respect your point of view. I respect mine as well.
-
@MasterLeo29 Be my guest
-
We know, @Pesala . We are just discussing some applications for it that we like - for me, the quick commands launch. It might seem "too much", but I guess it shows that we like Vivaldi's Clock
And yes, it might be just a "small addition", but some people really like it. For example, a coworker of mine heard from me that the clock is coming to stable and he loved it because it makes perfect sense for his workflow -
What is that thing, that on Twitter is an automatic log-in? I don't want that. I have not allowed that!
-
Recent Vivaldi snapshots don't render don't render form elements properly - text and password input fields and drop-downs that have white (#fff or #ffffff) specified for background colour, and those that don't have background colour specified at all, are rendered with black background, usually making the text in them invisible (unless selected). This might be because I use high contrast theme in Windows, however if Vivaldi is overriding background colour, it should also override the text colour.
Here's a test page, and this is how it renders for me:
-
Is there a new VB-nnnnn for remote X11 not working (with --no-xshm --no-sandbox being a current work-around), or does VB-61700 carry the weight of this new info? I ask because the current work-around is different than before and so could indicate that a different fix is required.
-
AdGuard VPN shut down browser every time when it's on and try to open page.
other snapshots are goodhttps://chrome.google.com/webstore/detail/adguard-vpn-—-privacy-sec/hhdobjgopfphlmjbmnpglhfcgppchgje
-
@mtaki14: Internet Download manager module has an erratic behavior, not observed in any other of my installed alternative browsers (firefox, edge, opera). Sometimes it is activated twice, some other times vivaldi's download manager is activated at the same time, at times it jumps out of the download page and so on. In the end it does download, but it is not its usual behavior.
-
@nutcracker And that worked fine in previous builds? Maybe it would be worth reporting regardless. It could also be due to the slight differences in the new engine version. Does it work fine with the equivalent Chrome version?
-
@mtaki14: Yes, it worked fine and normally in previous builds. To tell you the truth, I did not test it with Opera chromium 81, since I hadn't any problems in Vivaldi. In Opera chromium 82 it works as it should. In fact I didn't even install Vivaldi v.1848.4 (the previous one) after reading that it had some problems with extensions. Instead I jumped to this one (the latest) after reading that the extension regressions were solved. Perhaps it's not the chromium build because it worked just fine two builds before (still chromium 81).