In turn, the community is not able to reproduce this bug. They are often unaware of all the backend dependencies. As you know, most user are not developer. In turn, those end users reported the bug only with the subdomain steps. So why is it not fixed? My guess is that the users who reported this but with subdomain names were unaware of the required first steps to reproduce. If you're a developer interested to contribute to resolve this challenge, this pull request might be of interest at Better URL Matching #2517įor more than 2 years, this bug was frequently reported to the Dark Reader (DR) community. And before it does so, DR will not notify you about this. In the future, until this bug is resolved, this is your reminder that if you deactivate DR for a domain name, DR will automatically disable itself for all its subdomaines. You successfully temporarily resolved this challenge :) Using DR, toggle to Enabled for this website. Using FF, go to the subdomain, in this example, go to Leave DR other settings to their default. Which is showed by the number 3 in this screenshot below. Using Dark Reader (DR), toggle to Enabled for this website. Dark Reader works with all of those browsers. But Ungoogle Chromium has much stronger privacy and stronger security than Chrome.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |