Fix for Windows media issues – Vivaldi Browser snapshot 1929.3
-
@npro Like this:
It doesn't even need to be set in the flags when it works properly. As I said, native notifications worked for me properly since they were introduced (I only use snapshots), with 2 exceptions that left a series of snapshots broken with just Chrome notifications. The snapshot I am using now is the latest one to work properly I believe, after it the rest of the builds are broken.
-
Hello there
Certainly not. You are running Vivaldi on windows. According to @npro his issue is on Linux:)
-
@t0yz That's not a standalone, that's a typical default install for all users
-
@lamarca My standalone Vivaldi is on Windows, it's there in my signature, also I said about writing entries in the registry -which is clearly a Windows thing- and also mentioned Windows 10 Action Center, and I directly replied to Gwen who mentioned her Vivaldi installations on Windows
The Chromium notification on Windows is at the bottom right, the native notification on Linux is on top right, is it clear for you now?
-
@npro Noted
-
@npro I never mentioned anything about standalone. I have no idea where it came from. I only mentioned the regression with native notifications not appearing.
I am somewhat sure I can make those appear with standalone too given the correct snapshot, I can check it out when I get home.
Edit: standalone doesn't seem to be able to do native notifications. I've tried with 1874.27 and standalone only does Chrome notifications. Once I install it normally, I get native notifications.
Problem is, next versions, i.e. 1906.3 and above, are unable to do native notifications, standalone or installed.
1874.27 can, once it's installed.
-
Oh right, while I was confirming Gwen's lack of native notifications in standalone versions I thought your quote was referring to every install type, didn't read the original, sorry
-
the freeze problem seem to be fixed! thaks!
-
There's a problem with password autofill drop-down in this version - it's completely red (text and background), the only visible thing is the favicon.
-
@ender85 Is that on any login (doesn't happen here) or a particular site - if so, which?
-
@ender85
That happens on which Vivaldi page?
Did you tried in Vivaldi the Private Window mode to restrict any extension causing this?
Do you use a external password manager software (may inject logins)?
-
It happens on all sites as far as I can tell; this may be related to me running Windows in High Contrast mode.
The issue also happens in a Private Window (where only uBlock Origin is loaded), and I don't use any external password manager.
-
@ender85 said in Fix for Windows media issues – Vivaldi Browser snapshot 1929.3:
this may be related to me running Windows in High Contrast mode.
I will try this with High Contrast.
OH! Yes, true. For me it is red background, too.
Same on Chromium 83 so its is a Chromium core bug.I will report the bug to Chromium bug tracker.
And i reported teh bug to Vivaldi bug tracker.
-
I reported the Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1088291
And Vivaldi bug:
VB-68097 "Login field is completely filled with red" with highes Priority as it is a accessabiliy
issue!
-
Thanks. I've seen unexpected red backgrounds in some other places in Vivaldi (mostly buttons while holding down the mouse button over them), but can't find any right now.
-
@ender85 If you see one, please tell me the URL, i can add them to reports.
-
That's the problem – I've definitely seen it a few times, but now can't remember where. I'll take a screenshot the next time I encounter it again.
-
@ender85 Thanks, nice finding this bug and reporting to us, very helpful for bug hunting in Snapshots.
At this time there is not no need to give me a screenshot as the issue appears on all sites. The bug reports made were clear enough for developers to check and fix.
-
@ender85 Bug is now confirmed by Chromium developers and they work on a fix for chromium 83 code base, means Vivaldi 3.1 can get a upstream fix.
//EDIT: May be fixed in Vivaldi when changing to Chromium 84 code base (Chromium developers do no want to fix it in Chr 83)
