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

Chrome / Chrome Web Store claims Extension will no longer be supported #281

Open
cookieo9 opened this issue Jul 31, 2024 · 7 comments
Open

Comments

@cookieo9
Copy link

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:

  • The extension hasn't been updated (or at least uploaded to the store) in over a year
  • The extension needs to migrate to Manifest V3
  • Maybe one of the requested permissions is being deprecated for being too broad (Read Browsing History)?

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.

@samodovdi
Copy link
Collaborator

hi @cookieo9! Thanks for pointing this out. I'll look into this issue soon.

@ConcurrentHashMap
Copy link

@samodovdi Any update on this?

@samodovdi
Copy link
Collaborator

@ConcurrentHashMap still working on this, migrating extension to manifest v3

@cookieo9
Copy link
Author

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:

  • version 129 behaviour
  • Dev channel behaviour
  • slow rollout behaviour
  • I have opted myself out for now

@billgilligan
Copy link

Had my extension turned off b/c of the lack of Manifest v3 support early this week. Any word on a supported version update?

@samodovdi
Copy link
Collaborator

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

@Alukard-X
Copy link
Contributor

#287 (comment)

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

6 participants