Please restore options to Block notification and location requests

[booopera]

booopera last edited by

In recent versions I have only the option to "Ask before accessing/sending (recommended)"
Other than that, I can only Allow or Block sites individually or by TLD. Either way gets messy.
The "Allow" option indicates possibility of a blanket block, but I haven't found it.
To turn off a requirement for sites to ask before using locations/notifications sounds like a blanket "allow".
Please return "block" as an available default option in locations/notifications.
Thanks

[leocg]

leocg Moderator Volunteer @booopera last edited by

You turn the switch off and you are blocking it.

[booopera]

booopera last edited by

Thanks for your clear and unequivocal answer.
My request still stands, though - now as a request to word the option more intuitively. Everyone I have asked to look at the options assumes that to turn off the requirement to ask first would give automatic approval, not denial.

[booopera]

booopera last edited by

The option for Flash still appears to read intuitively:

• Allow sites to run Flash off/on
• Ask first (recommended) off/on
  No doubt about the meanings there.
  Turning off Ask first means allow; however, the ask first switch has no effect on the setting displayed. It reads ask first, whether switch is off or on.
  Have mercy on us!

[burnout426]

burnout426 Volunteer @booopera last edited by

@booopera said in Please restore options to Block notification and location requests:

Everyone I have asked to look at the options assumes that to turn off the requirement to ask first would give automatic approval, not denial.

By default, a browser would never allow sending a notification without asking (especially with a global option). Knowing this, the current wording should make more sense. However, I admit it could be better as not everyone will know that.

[leocg]

leocg Moderator Volunteer @booopera last edited by

The current behavior was implemented due to several users requests. They say that changing the setting string when turning the switch off or on cause confusion.

[A Former User]

A Former User last edited by

Not allowing users choose an option not to be disturbed by each website requesting notifications are way too amateur for Opera Browswer. I guess for other browsers this feature is more important than it is to them..

[sgunhouse]

sgunhouse Moderator Volunteer last edited by

@yannisdran Apparently you don't want to read - disabling notifications is easy.

[booopera]

booopera last edited by

Easy, yes, although not as clearly communicated as I found the older settings.
Opera mobile for Android still offers:

• Ask every time
• Allowed
• Denied
  Who could misread that?

[burnout426]

burnout426 Volunteer @leocg last edited by

@leocg said in Please restore options to Block notification and location requests:

The current behavior was implemented due to several users requests. They say that changing the setting string when turning the switch off or on cause confusion.

Hmm. It Chrome it switched to "blocked" when you turn it off. Doesn't seem confusing to me.

[leocg]

leocg Moderator Volunteer @burnout426 last edited by

Opera used to do the same and for me it was fine. The problem is that some people looked at it saying 'blocked' with the switch tuned off and seemed to understand that they were allowing something and it was confusing them.
That's why Opera changed the behavior.

[burnout426]

burnout426 Volunteer @leocg last edited by

@leocg Hmm, they must have thought that "blocked" meant to block the asking and allow automatically or something. Of course, with the current wording, when you disable, it sounds like the same thing. It sounds like you're disabling asking and allowing automatically.

Given the way the toggle and exceptions actually work, I think it'd be more like:

On=Ask to add site to allow/block list.
Off=Add site to allow/block list manually.

But, that's just me.