Minor update (3) for Vivaldi Desktop Browser 5.6

DoctorG

@Omnimaxus The issue is already reported, but i think it is no serious bug, more of a cosmetic issue.
We all have our pet bugs which need to be fixed.

DoctorG

I see that the issue with the 🪲 black borders in fullscreen are fixed in internal 5.7 Daily tester version.
I hope a next 5.7 Snapshot could get the fix for you users.

DoctorG

️Please, do not report more bugs to bug report page with 🪲error message 'Minified React error #185'
We have enough in bug tracker.

Omnimaxus

From a coder's perspective, maybe not all that "serious." But from an user's perspective? Sure. It does interfere with the overall usability and/or user experience with Vivaldi as a whole. People like to see "polish" in what they use, especially on a daily basis. I liken this to a car that may function just fine, but happens to have a ripped-out hole in the driver's seat or even the side passenger's seat. That would scare off a great many potential buyers, I assure you. The quality of the car would be brought into question. Same with Vivaldi and users who may not be as "technical" as those who develop Vivaldi. Luckily, I'm sufficiently technical (I can build computers and have done some light programming back in the day) to understand that this is a "cosmetic" bug and doesn't bear on the actual functionality of Vivaldi, but at the same time, it's a distraction (the black edges and the black screen that comes up when viewing the settings window), and given that it's unattended for long enough (as a "bug"), it'd make me wonder (as a supporter of Vivaldi) where the developers' priorities lie, and if they truly understand the critical importance of the user experience, too. This isn't the first time this issue has come up. Really wish you guys would defer to users' concerns a bit more in this regard, and take care of UI-related "cosmetic" bugs before stable releases. Thanks.

DoctorG

@Omnimaxus I can understand what you mean: some issues are cosmetic and some are really breaking usability more or less.
We testers are trying to hunt as many issues as we can, report them to internal bug tracker and test users reports reaching the bug tracker.
But testers have no influence on priorities of bug fixes, that is on developers team side, they decide hat has to be fixed first.

enc0re

@DoctorG Providing fix for bug with missing borders, which actually introduces another bug and won't fix previous bug and then putting that issue on side note, because it is not so important is really weird approach of development

DoctorG

@enc0re said in Minor update (3) for Vivaldi Desktop Browser 5.6:

weird approach of development

Your personal opinion and freedom to express your feelings about a browser and its development.
Oh my goodness, testing and bugfix workflows are so different.
If you have some positive critics and ideas for a better workflow, please open a new thread.

deneban

@Ruari, please include the version in these minor update postings, especially if there are a few in a series, so we know if we have the latest or not.

Pesala

@deneban It has been asked before, several times. One can see the version number in the Status Bar before downloading it.

Version Number.png

deneban

@Pesala Great, but I want to know what version this web page is speaking to.

Pesala

@deneban So, open the download page, and hover the mouse cursor over the download icon. That must take about five seconds.

deneban

Periodic Reload:

Why are the "Disable" items removed from the Periodic Reload tab contextual menu? How do we stop periodic reload?

I am no longer seeing a periodic reload progress bar on my tabs. I am trying to verify if reload is even ocurring.

Pesala

@deneban The Disable and Disable All options are only available on a tab that is set to reload periodically.

deneban

@Pesala Very well, but why keep it as a hidden secret? and moreover why not be consistent with the snapshot pages?

deneban

@Pesala That's a 3rd problem, I can't seem to get any tab to periodically reload.

95phil

I'm not sure if this is a bug. But there seems to be a glitch while scrolling toward the left of the tab bar using the touchpad but the issue does not occur while scrolling toward the right of the tab bar.

While scrolling toward the left the scroll does not move how it used to move earlier but instead moves to the left and then scrolls back to the right and does not allow one to scroll to the required tab. It often takes multiple tries to land at the required tab which can be frustrating. But the scroll towards the right works smoothly and functions how it is supposed to which is quite puzzling.

This was not present in the earlier versions but seems to be an issue only with the current version. I use two-level stacking with the tab bar positioned at the top.

If anybody could let me know how I could resolve this issue or if others are also facing the same issue then that would be really helpful.

colebantam

@Ruarí
Can we expect a Chromium 108.0.5359.179 based Security-Update today?

Ruarí

@colebantam We are working on an update yes

colebantam

@Ruarí
Thanks