@kirdomin
Hi, no problems with Vivaldi 5.2.2623.26 (Stable channel) (64-Bit) on Windows 11.
Check if Google Service Token is still enabled in vivaldi://settings/privacy/
May you can check with a guest profile, it exclude all settings and extensions.

https://help.vivaldi.com/article/guest-view/

Cheers, mib

@kleinbus Nope. You would have to have exported the passwords as a human-readable file in order to import them.

@pafflick Updated... it's fixed! Thanks 🙂

@franckv said in bug : pinning of stacked tabs is broken after today update:

I need someone from Vivaldi to tell me which one it is

Ipso facto...

maybe consider raising either a bug report or a feature request?

As a general rule, Devs do not frequent the forum threads, so your wonderment here alone is likely to be unfulfilled, whereas if you raise it formally [a forum post is informal, in this context] you stand a better chance of attention [eventually...].

Otoh, it's not impossible that one of the kindly generous ever-indulgent [🤭 ] Mods might see your words here, take pity, & make a behind-the-curtain enquiry of a Dev.

@doctorg I use both a local windows app and a web based DAW (recording app). The web app audio is choppy with a device buffer of 1024 samples just like all other audio in Vivaldi at 1024: youtube audio, amazon music, etc.
It doesn't matter if I have been recording or not. When I set the device buffer to 128 in the driver, the audio in Vivaldi is fine. When I set it to 1024, the audio in Vivaldi is choppy.

Hey,

I now have exactly the same problem since months: blackscreen when monitor starts power saving (not waking up anymore, no display connect till next cold reboot). Also tried everything and nailed it down to Vivaldi, all other installed browsers work normally...

Seems to also depend on AMD display driver version! Last working driver was/is 21.12.1 All drivers after that caused blackscreen when display wants to go sleeping. Told also AMD via bug feedback, but no bugfix in drivers since (possible?).

Specs: AMD 5800X, Asrock B550, AMD Radeon 6600XT, EIZO CS 2420, Win 11

Could you please have a look into this?

@mib2berlin I was wrong the problem still occurs.

@pathduck OK. I found that, it is a long time since I set up the mail client.

Still not able to reproduce in a clean install. This may have to wait until my mind is clearer.

@loudermp I don’t see ID.me stuff, what is it that you are trying to do anyway?

@tbone-15 "Folder-app launch" would be going to the physical folder on the hard drive and double-clicking" the .exe file in the application folder. "toolbar-launch" should have said "taskbar-launch." It's opening Vivaldi from its taskbar icon.

@kikey Same request: https://forum.vivaldi.net/post/540097

Finally got to spend some more time on this again. (I was gonna ask about the recent closed tabs and all, ...but) I renamed History (as the command parameter) to 'Show All History' and applied your suggestions as well. Once I got to that dropdown on the commands over on the right side, and with your tip to just drag them over, I'm all set. Very much appreciated !!![renamed params.jpg]
.
renamed params.jpg

@doctorg Thank you for your answer. I will try to ignore it in the meantime.

@valiowk There's definitely an issue searching for images with Bing/Google in Private windows and Guest windows (Bing only in Guest).

I've tested with both 5.2 Stable and 5.3 Snapshot. The search engine implementation has been changed a lot between these versions, but the errors seem similar - looks like it does GET requests when it should do POST, or something like that.

The image search engines in 5.3 are really new, and I'm sure stuff like this will be straightened out over time.

EDIT: I've also tested with Private windows in 5.1 and 5.0 and the same thing happens, so this issue has likely been around for a very long time.

I'd say report a bug, it's probably a known bug but but I've not heard about anyone else reporting it. Make sure to specify and test in 5.3 Snapshot - IMO reporting a bug for image search in 5.2 Stable is kinda pointless now that the SEs have been reworked for 5.3. Better to focus on getting it right for 5.3.
https://vivaldi.com/bugreport/