Confirm Window Close dialog not remembering choice for "Don't show again" checkbox

[britechguy]

Hello,

I am running Vivaldi version 5.4.2753.47 (Stable channel) (64-bit) under Windows 10 21H2 Build 19044.1889. In the Vivaldi About dialog, the command line is shown as:
"C:\Users\brite\AppData\Local\Vivaldi\Application\vivaldi.exe" --disable-features --enable-features --save-page-as-mhtml --enable-features --disable-features --flag-switches-begin --flag-switches-end

Ever since the last "major update" not all that long ago the close confirmation dialog on private windows

has refused to honor the Do not show confirmation again checkbox.

At first I figured that this was a bug that was introduced and would be fixed, but it hasn't been, so I'm finally breaking down and asking if anyone else has experienced this and, if so, if there's anything that can be done to make Vivaldi honor the choice one is making by checking that checkbox?

This has never happened before, and I've been using Vivaldi for several years now and through multiple versions.

Thanks for any assistance and insights.

Brian

[Pesala]

@britechguy I can confirm the bug, but it seems like an unimportant issue. If you no longer want confirmation for closing windows, then set the option in a regular window. Then private windows will also close without confirmation.

What would be the use case for wanting confirmation for regular windows, but not for private windows?

[britechguy]

First, thanks for this tip, as it has solved the problem.

It's an "important issue" to me simply because I haven't had this dialog appear in years, and suddenly it was again. I don't tend to use multiple regular windows, and on those occasions I do I most often exit Vivaldi and don't get warned about anything since I have things to resume exactly where I left off when Vivaldi is invoked again.

Now that I've followed your instructions all is solved. I'm thrilled and glad to learn that the fix was this simple!

[Pesala]

@britechguy Bugs are unlikely to be fixed if they are not reported. If you think it needs fixing, please see How to Report a Bug.

[britechguy]

@Pesala: You're absolutely right. In other venues I have said to others precisely what you have said to me, and I thank you for the link to the "How To" for reporting issues. At the very least I now need to take a look to see if it may have already been reported, and add a comment if it has. If not, then I need to open a new issue/bug report.

Addendum: Filed Bug Report [VB-91451]