Open AliRezayiNejad opened 1 month ago
I have investigated this issue and unless I am misunderstanding, this is intended and semantically correct.
In order to match both www.example.tld
as well as example.tld
you can simply use example.tld
and it will handle both domains correctly.
*.example.tld
does
example.tld
(imagine you have fixes for app.example.tld
hosting an entirely different application).www.example.tld
, which is semantically correct.example.tld
captures both example.tld
as well as www.example.tld
.Yes, now my list is full of duplicate urls like example.com
and *.example.com
.
The way it used to work was more reasonable.
Because example.com
, foo.example.com
and bar.example.com
generally use the same style.
If not, in rare cases, just add this special case to another list.
Prerequisites
Bug Description
(At least in "Invert listed only" mode,) Using .example.com will affect www.example.com and any subdomains like sub1.example.com. However, If a website omits the www. part from it's URL (like archlinux.org), then the .example.com format does not affect the site, a separate entry of example.com must be created for that. This behavior is consistent on Firefox on multiple platform.
Website Address
archlinux.org vs aur.archlinux.org or any other websites like it
Steps To Reproduce
Expected Behavior
Either the main domain of both websites has to be affected by Dark Reader, or neither. I personally prefer both.
Actual Behavior
archlinux.org is not affected by Dark Reader, while darebee.com is. This behavior is consistent for all similar websites, based on how they handle the "www." in their URL.
Screenshots
No response
Operating System
Windows 10, Arch Linux, Android
Web Browser name and version
Firefox 125.0.3
Dark Reader version
4.9.84
Additional Context
No response