-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
This extension may soon no longer be supported in Chrome #92
Comments
Hope never dies but the latest update dates back to January 9, 2022. Sadly, I think it's time to consider this project abandoned. |
There's a Draft PR started back earlier in this year on the |
I hope I find the time to look into it the upcoming weeks. |
Hi @badsgahhl and thanks! PiHole Browser Extension is very useful and well done. |
yes very useful |
just wondering if there is any update on this as 2024 is closing. |
As mentioned, I really don't use PiHole on my own anymore and therefore I reprioritize this project further low in my daily schedule. I started with the V4 Implementation but still needs fine-tuning. Mostly Manifest V3 ist breaking a lot of stuff. Really have no time when this is going to be released, sorry to say. |
@badsgahhl Are you open to contributions to the extension? Since I actively use PiHole, I wouldn't mind daily driving the V4 implementation that's WIP and opening a PR to fix whatever breaks. |
Since the V4 branch has a lot of WIP refactoring, I've forked With the changes I've made basic functionality is working. I'll keep testing my branch and see if I hit issues. All behavior should be same as original, except the check status interval changed from 15 to 30 seconds due to limitations of the |
Will look into that! |
Thanks a lot for the work! Updates will be pushed throw the stores in time. |
Chrome is phasing out support for Manifest V2 extensions. In order to continue working in Chrome this extension will need to migrate to Manifest V3: https://developer.chrome.com/docs/extensions/develop/migrate
The text was updated successfully, but these errors were encountered: