-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
why was Blacklist support removed? #36
Comments
Any update ? |
@Bonjour123 As far as I could tell it's because chrome.proxy is now used and that only has a bypass list option. |
pac script can set proxy only for some domains. |
The blacklist UI is a mistake. I did not write any code for the blacklist feature. Ten years ago, all Chrome proxy extensions had bugs, so I wrote my own. I may add Manifest V3 support for this extension in the future. |
Thx henices, I will take a look if I have time soon to see if I I can generate the pac file on the fly to generate the blacklist. @henices I already have manifest 3 running on my fork. But I changed how it starts a proxy by moving more stuff to the background js so it won't be a copy paste. Also added a feature that I needed so that I won't be able to access some sites without the proxy on. |
I saw that in commit ccf3a2f
Blacklist started to be removed as an option. and with some commits after that, it got fully hidden as an option with only whitelist remaining.
But I can't find any issue/pr on the reason why. I wanted to use this extension to only enable the proxy on certain websites. So this option would be usefull for me.
Is there a technical reason to not use it?
The text was updated successfully, but these errors were encountered: