Solved Website permissions confusion

lovegirin

Why doesn't this work?
It also doesn't work to put

[*.]youtube.com:443
https://[*.]youtube.com:443
and probably a few more I tried but can't remember.

There are several ones I've added through the address bar padlock that look just fine:

What is the proper syntax for adding them manually in Settings -> Privacy and Security -> Website Permissions?

Pathduck

@lovegirin Unfortunately, you can't use wildcards there, and these are not the same
https://example.com
https://www.example.com

I have reported this as a bug:
VB-104805 Website Permissions - unable to use Chromium-style wildcards for domains

It is confusing to users since there are several different ways in Chromium to set permissions, depending on what type it is.

For instance, camera+mic+location permissions do not support wildcards and can't be added manually in Chromium in any case.
https://example:443

While for Cookies/Notifications and other they use the wildcard syntax:
[*.]example.com

For the permissions where Chromium allows users to add directly, they support wildcards, while for those where they have to be set in the SiteInfo dialog, they use the former syntax.

So you get a confusing mix of syntax styles:

DoctorG

@lovegirin Use https://youtube.com

The Chromium-like regex/wildcard is not implemented in Vvialdi UI.

lovegirin

@DoctorG would https://youtube.com mean the same as *.youtube.com or would I have to add a rule for every single subdomain?

Pathduck

@lovegirin Unfortunately, you can't use wildcards there, and these are not the same
https://example.com
https://www.example.com

I have reported this as a bug:
VB-104805 Website Permissions - unable to use Chromium-style wildcards for domains

It is confusing to users since there are several different ways in Chromium to set permissions, depending on what type it is.

For instance, camera+mic+location permissions do not support wildcards and can't be added manually in Chromium in any case.
https://example:443

While for Cookies/Notifications and other they use the wildcard syntax:
[*.]example.com

For the permissions where Chromium allows users to add directly, they support wildcards, while for those where they have to be set in the SiteInfo dialog, they use the former syntax.

So you get a confusing mix of syntax styles:

lovegirin

Thanks for your reply!
That is so frustratingly annoying and confusing...

Qwertie64982

Thanks for reporting that as a bug!

At some point this was moved from Chromium settings UI to Vivaldi's settings UI. All of my rules appear to have been migrated over with the wildcard intact. I guess this means that suddenly all of my rules are broken, if the wildcard is not implemented in the Vivaldi UI? That seems like a significant oversight...luckily in my case it defaults to deleting cookies rather than saving them....

And I agree, the mix of styles is confusing at best.

As always, thanks to the devs for all their hard work though!