-
Notifications
You must be signed in to change notification settings - Fork 38
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
Chrome / Chrome Web Store claims Extension will no longer be supported #281
Comments
hi @cookieo9! Thanks for pointing this out. I'll look into this issue soon. |
@samodovdi Any update on this? |
@ConcurrentHashMap still working on this, migrating extension to manifest v3 |
An update on the client-side. I had a devel version of Chrome OS (version 129) which turned the extension off, but I was able to manually re-enable it in the Extensions screen. Stable versions of Chrome OS (127) and desktop Chrome (128) don't do this for me, so it's either:
|
Had my extension turned off b/c of the lack of Manifest v3 support early this week. Any word on a supported version update? |
hi everyone! I'm lack of time now, I'll push draft pull request with the changes so you can track the progress or maybe someone can jump in and add some contribution |
According to the Chrome Web Store page for the Feedly Extension and the extension page chrome://extensions/?id=egikgfbhipinieabdmcpigejkaomgjgb in Chrome itself, it seems like the Feedly-Notifier extension will be removed from the Web Store and disabled in the browser at some point in the near future because "it doesn't follow best practices for Chrome Extensions".
I'm not 100% sure why this is the case, although I can think of a few reasons:
It may be the case that the official contact for the extension may have been sent details on the issue.
In any case, I fear that the extension will suddenly stop working, and although I can manually install it, as well as re-enable it where it's still installed, I'd rather not go against the recommendation of my browser vendor without good reason.
I don't see any deprecation / EoL messages here or on the store page so I'm assuming that this extension wasn't intending on going away. But if that is not the case, and I should look elsewhere for either a new plugin or a new RSS reader service, it would be good to know that too.
The text was updated successfully, but these errors were encountered: