Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Element Picker for Per-Site Exclusion Rules #48

Open
lhl opened this issue Nov 30, 2016 · 9 comments
Open

Element Picker for Per-Site Exclusion Rules #48

lhl opened this issue Nov 30, 2016 · 9 comments

Comments

@lhl
Copy link

lhl commented Nov 30, 2016

Hi, just discovered Dark Reader, and it's great. I didn't see this in the issues, but I'd be interested seeing what the interest/feelings are on support for more extensive per-site customization/overrides.

Ideally, it'd be nice to be able to adjust some of the rules (like contrast) on a per-site level, and on a per-element basis (using an element picker) - is anyone using Dark Reader w/ Stylish? Maybe there's easy ways to carve out exclusions that way.

Otherwise I'd be interesting in forking and doing some work on a version that has some of this functionality, maybe also making the ignore/darksites JSON file be something that could auto-update/be customized - I see some pull requests there? Just wanted to see what you think before I get started @alexanderby

What's the darkreader license btw? There are some plugins that already have some functionality, but uBlock for example is GPLv3, and there might be other code that'd be useful that's MIT licensed.

@brodock
Copy link

brodock commented Dec 15, 2016

Being able to pick elements (or adding the XPATH or selector rules on a site) would be super useful. There are elements that are already "darker" and I don't want it to have inverted colors (like the gitlab.com code highlighted blocks).

@alexanderby
Copy link
Member

I've started to work on another inversion engine, so I hope that specific per-site fixes should have gone.

There are so many specific cases, so I think it's too hard to create such a picker, and create a system, that will auto-merge the fixes. So, currently it's faster to open Chrome Dev Tools, determine a selector for elements, that shouldn't be inverted, and add it here https://github.com/alexanderby/darkreader/blob/master/src/config/sites_fixes_v2.json

@alexanderby
Copy link
Member

Maybe Chrome Dev Tools picker it a better choice, because more information is needed to determine which selector suits better. Here is an updated doc for modifying per-site fixes https://github.com/alexanderby/darkreader#how-to-contribute

@elypter
Copy link

elypter commented Jan 26, 2019

why not copy the one from ublock origin?

@Gusted
Copy link
Contributor

Gusted commented Jul 25, 2020

why not copy the one from ublock origin?

License and we will be publicly shamed for stealing code :).

@elypter
Copy link

elypter commented Jul 31, 2020

cant they just switch from mit to gpl?

@Gusted
Copy link
Contributor

Gusted commented Jul 31, 2020

cant they just switch from mit to gpl?

That is not how it work...

@DatHypnoboi
Copy link

I desperately want this to be added

@ggplayer0
Copy link

ggplayer0 commented Dec 7, 2024

Honestly, this not being implemented in some form is the only thing keeping me from using this extension on a regular basis. Navigating through the dev tools just to fix one part of a page is a frustrating experience.
Would there really be a licensing issue with using the selector from UBlock Origin? It seems like the licenses should be compatible. I'm not exactly a legal expert though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants