Thanks for the info. @nomadic

@Pathduck Saw your latest posts about that. Here, saw the Temp is on %User% Local Temp with a random number if I recall. All the AutoUpdates work fine, and since less than a month there are 2 different Snaps and Stables versions altogether. AutoUpdate is launched manually till now, need to check the New Task. It appears with a random number as well. Saw entries for the Latest, maybe the latest versions updated, as you comment, but since doing other tasks didn't looked deeply to understand the routine. Will check in next days, and between next updates. -- Bothered? Cricket 🏏?....

@Zalex108 I like how you made a screenshot of the ScreenShooter 😄

With Vivaldi you don't need a mac, OpenBSD, FreeBSD or any extension. Just hover Over the image Rt Click, or however you get the context menu use Image Properties (the image will open in a New Tab) Again hover over the image, get the context menu and Copy Image open your favourite image manipulation program (IrfanView is a good one and works well with Wine on Linux) Create a new (empty) image and Paste I believe many programmes have hundreds of formats you can Save As...

Update! ☀ / 🌙 Schedule Shortcut

Bookmarklet : Share the web page on Vivaldi Social

@potmeklecbohdan said in V Folder Icons: @Zalex108 If you do this, only Dolphin will work… (i.e. I tried it with the two FMs and only Dolphin worked) Thank you. I will add it on the How to. 👍

@Zalex108 See ☛ https://adblockplus.org/filter-cheatsheet#elementhideemulation

@tealing said in Guide | Vivaldi Search and Suggestion URL explanation and tutorial (simple).: 5 maximum suggestions Yes, Seems like 5 maximum suggestions.

for current Chromium 93 policies with ...WhiteList... in name are renamed to ...AllowList.... Similar with …Black… changed to …Block… Please investigate more on your side - if you know news on changes, feel free to answer.

@lonm From the reddit Mixpanel quotation: "We immediately began investigating further and learned that the behavior the customer was observing was due to a change to the React JavaScript library made in March 2017. This change placed copies of the values of hidden and password fields into the input elements’ attributes, which Autotrack then inadvertently received. Upon investigating further, we realized that, because of the way we had implemented Autotrack when it launched in August, 2016, this could happen in other scenarios where browser plugins (such as the 1Password password manager) and website frameworks place sensitive data into form element attributes." Note that Mixpanel indicates the 'harvesting' was inadvertant (and I have no direct reason to disbelieve them). However, it raises the issue of companies that can do the same sort of things deliberately... or of 3rd-party scripts in popular website code that can do it. As for me, I'll continue to keep my script-blocking shields up except in certain, carefully-vetted, specific situations.