Why I cannot open custom theme settings for a single site? #10082
Replies: 2 comments
-
The editor is intentionally fairly simplistic because it is not intended for general use, just for development of fixes prior to checking them into a repository and filing PRs on GitHub. In the past I was considering adding an option to "filter" fixes based on a pattern. Basically like a "search" box, which would accept a URL or a fragment and would hide all rules which do not match it. Would that work for you? If not, could you describe a solution you would like to see? |
Beta Was this translation helpful? Give feedback.
-
On a similar note, how difficult would it be to implement an include file hook into the filter files so that users could edit and store their own personal include (even with the same formatting as this one) for private websites? For such websites users would never be allowed to file a PR with the fixes to the filter configs, and having a hook to an external include would prevent the browser extension to ever overwrite any customization in case the add-on is updated. |
Beta Was this translation helpful? Give feedback.
-
firefox or chrome latest darkreader, I am not able to open the editor in single site mode,
no matter if I have selected for this site only or for all sites, after clicking dev settings, it always only opens the editor in "all sites mode"
Beta Was this translation helpful? Give feedback.
All reactions