Domain-based (instead of subdomain-based) per-website settings

As a separate point, functionality like this should likely incorporate the public suffix list to understand the domains where a "line" should be drawn between per-site preferences.

(Info at https://publicsuffix.org/)

This is one of those examples where allowing it per subdomain would increase complexity (of code/interface) dramatically, for a small benefit (in terms of number of users affected). Most users are happy yo be able to set a setting for 'google.com' and have it apply to all subdomains.

Such kind of requests should be delegated to adblockers like uBO. Orion, as a browser, need to provide functionality that considerable user base may want/need.

jrose oh you are actually right - I was confused by your title as it suggest adding support for subdomain based settings,vs what you want is domain based settings?

Instead of following something like Public Suffix, an alternative could be like this:

• youtube.com matches just youtube.com
• *.youtube.com matchesfoo.youtube.com, but not bar.foo.youtube.com
• **.youtube.com matchesfoo.youtube.com and bar.foo.youtube.com
• *.com matches foo.com, but not bar.foo.com
• **.com matches foo.com andbar.foo.com

It may seem complex, but it's quite similar to how grep works. Most users wouldn't need to understand this fully either in order to use it.

eirk This would have to work at a website settings (gear icon) level. So either we do it at domain level (matching all subdomains automatically) or at a subdomain level (like it is now)

Hey all, brand new here and really liking Orion. Quite refreshing.

Came in here looking for this issue. Like @jrose and some others I really do like the option to drive around without javascript turned on by default. I also get that as users we are the edge case and there are only so many engineering hours in the day.

I know it's hard to change functionality from the way it is today to maybe the way a lot of other products function. If you look at uBlock, et al, they give you the option to get pretty specific with wild cards, etc. — obviously that kind of fiddling is a power nerd thing and breaks how domain matching is right now. Others match subdomains by default (so politics.slashdot.org is off when slashdot.org is in play). I also get that wildcards can be a slippery UX slope.

I have a UX suggestion that would keep functionality as it is today but also allows some fine tuning.

The use case here goes back to slashdot.org — every time you open something in one of these subcategories it adds a host name to the naked domain.

So Devices = devices.slashdot.org and so on.

With Orion currently, I have javascript turned on for this domain, and zoom set to 115% to 125% depending on how old my eyes are feeling on any given day. Every time I jump to a subdomain I have to turn scripting back on and ⌘+ a couple of times. It's also the same jarring when you move between example.org and www.example.org, my bank (www.bank.example.org and account.bank.example.org), and so on.

If I could, I'd suggest by default you don't wildcard the domain, checkbox off, that's how it works to today, and doesn't break the UX.

For the bit twiddlers you can give us the option to match everything, no more, no less. Anybody who's in at this level making changes isn't your average consumer Safari user anyway.

The words might not be right, nor the visual, but something as simple as this (or simpler) would keep most of the people happy most of the time.

Thanks for listening. For a pre 1.0 product this is a really smooth user experience vs. powerful feature set.

Vlad There is a limted number of them, why not just add them as rules and be done with it.

That's a valid thought, thank you.

While I can tweak one by one but it would be nice to do it once. The third time I have to do this to 5+ sub domains? I'm probably not going to and go back to Firefox. Especially if I forget all the tweaks for this one domain and then have to go hunting in settings trying to remember what I customized.

Could adding a save from the site properties be considered?

I guess even better is a switch up by Compatibility Mode that saves the state ("remember these settings"?) without having to click an extra button.

Again, thanks for listening.

julesallen Not sure what would that Save do?

A quicker change is to consider switching website settings to be domains+subdomain level instead of subdomain level as the OP suggests.

It would be great if we could set some settings for a whole domain including its sub domains. For example I usually disable JavaScript on corriere.it and any of its subdomains because they annoyingly refresh the home page after some time, while I'm in the middle of reading the news.

They have a lot of subdomains (usually one for every main city) and if I'm reading a news which is not in the home page and it's in a new city, I have to disable JS on that website too, like in this case:

It would be great if I could edit that field and just type *.corriere.it so the settings would apply to all its sub domains.

andreagrandi How would you imagine to be edit a feiled in a popup dialogue? Any example seen in any Apple app?

ie, keyboard shortcuts settings. apple has a lot of things that follow this kind of UX.

use glob pattern for adding configured websites under extension settings,
e.g. every page with the low level domain google.com (e.g. foo.google.com, bar.google.com) can be globbed as *.google.com

would make ux better by making users go back to configured websites screen less