Sub domain control

[sxp]

If I use to invert the only mode, I add xxx.com to the site list, then I visit sub.xxx.com, I don't want to invert this domain. I can't exclude it. When I use the shortcut key to toggle the domain, extension just adds or remove the sub.xxx.com from site list, but the page has no effect.

I suggest a feature:
If current need add domain is a subdomain of a domain that already exists in the list. Then we do the opposite of the parent domain(add the subdomain to a exclude list?), or we remove the parent domain from the list(When user go back to the parent domain, he can re-add it to the list).

If current need add domain is a parent domain of a exists domain. Then we add it to the list, and don't change the exists domain. (When the parent remove from list, the old subdomain will be saved in the list, so the function of the subdomain has no effect)

In general, I want to add some features to avoid frequent visits to a website, toggle dark reader, but no effect problem.
(Sorry for my poor English)

[RalphLesch]

If I understand you correctly, you want to include a domain, but exclude a subdomain or vise versa.
This is already possible, in both "Invert listed only" (include) and "Not invert listed" (exclude) mode:

Mode	Include	Exclude	List entry
include	xxx.com	sub.xxx.com	`^xxx.com`
	sub.xxx.com	xxx.com	`^sub.xxx.com`
exclude	xxx.com	sub.xxx.com	`^sub.xxx.com`
	sub.xxx.com	xxx.com	`^xxx.com`

Problematic is the case of including/excluding all subdomains except for one or more, like include "*.xxx.com", but exclude "www.xxx.com".
Currently, the only way I can think of, would be to add an invert fix (developer tools) for "*.xxx.com", and exclude "www.xxx.com" (in exclude mode).

For DarkReader, I would suggest to either use both include and exclude lists together or to change to pattern syntax, for e.g. full regex support (see my comment about the syntax).

Related: #147

[alexanderby]

^ meaning the beginning of the string works. What about both exclude and include lists, I plan to make unlimited count of groups with different settings.

[RalphLesch]

Sub groups for domains should be enough to solve most URL match problems.
I would suggest an extended hierarchy:

• common/shared group, with inversion fixes that are always used (unless deactivated by an option in the other rules maybe?).
• site / domain groups for URL pattern, will be used unless subdomain matches are found.
  • subdomain groups: overwrite (super)domain rules.

Then a layout like this is possible:

{
    "common": { "invert etc (fixes)": "", 
    },
    "sites": {
        "*": {
            "fixes": "",
            "subsites": {
                "domain1-pattern": {
                    "fixes": "",
                    "subsites": {
                      "subdomain1-pattern": {},
                      "subdomain2-pattern": {}
                    }
                },
                "domain2-pattern": {}
            }
        }
    }
}

You can probably combine "sites" with "*" to save one tree level.

Side note: collapsible sub groups in the editor and/or a complete separation for the sites (show only site config) would help a lot in the new UI.

[alexanderby]

Here is what I'm going to do with the list, similar to glob file patterns #373

[Gusted]

As of #2327 you can simply exlude an subdomain by !subdomain.example.com

[aogier]

Hi, I'm having probably the same problem here: I'd want to exclude github.com (which has his own dark theme now), but include docs.github.com, and this does not seem possible with the button.

[0xallie]

@aogier The solution was explained a few comments above. You can manually change the exclude list to have ^github.com instead of github.com.

[psarno]

I am unable to get this to work.

I have a "Not Invert List" with "twitter.com", because I am using their dark theme.

I want "blogs.twitter.com" to let Dark Reader handle it as their theme doesn't apply there.

I tried entering "^blogs.twitter.com" and "!blogs.twitter.com" in the list and they don't have any effect, it seems the presence of "twitter.com" already in the list prevents Dark Reader from working on the subdomain.

[Gusted]

Add ^twitter.com that will disable it just for twitter and not for any subdomains like blogs.twitter.com

[ackvf]

@RalphLesch

For DarkReader, I would suggest to either use both include and exclude lists together or to change to pattern syntax, for e.g. full regex support (see my comment about the syntax).

This is the first time I am seeing a mention about using both include and exclude lists together. How can I do that?

[megamorphg]

As of #2327 you can simply exlude an subdomain by !subdomain.example.com

If we can get "!" to work, this would be a great band-aid for now.
Currently "!" doesn't work to whitelist a subdomain (while the overall domain is blacklisted). Maybe ! URLs needs to be allowed precedence no matter where it is in the list?

[mattwelke]

Was talking in #7503 about my issue with the GCP console.

Here's a detailed explanation of my use case.

For google.com, I don't want to use Dark Reader because they support a proper dark theme. So I disable Dark Reader on google.com by clicking that rectangle button in the top left corner:

For cloud.google.com, I also don't want to use Dark Reader because even though their documentation doesn't have a dark theme, that site doesn't yet behave nicely with Dark Reader. I'm okay sticking to the site's default CSS.

So, on cloud.google.com, I could click the top left rectangle button to override how I disabled it for google.com:

But instead, I don't. I leave it alone:

For console.cloud.google.com, I do want Dark Reader enabled because it doesn't have a dark theme and Dark Reader just a good job creating one for it. I try to override the disable I did for google.com by clicking the top left rectangle button:

When I click the button, nothing happens. I believe that's the issue with subdomains I'm running into here. If I do the override of my settings for google.com at the cloud.google.com level (making it dark), then the console becomes dark and I can do another override at the console.google.com level to make it light. But that's the opposite of what I want. I want cloud.google.com to be light and console.cloud.google.com to be dark:

[Revadike]

same thing for https://console.firebase.google.com

[alexanderby]

Fixed by 5546bd5