-
Notifications
You must be signed in to change notification settings - Fork 44
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
Replace functionality with 'tabs' permission usage (required to restore Reedy in Chrome Web Store) #31
Comments
Which features don't work at the moment? Other than runtime errors being reported, Reedy seems to be working (most of the time). I initially thought it stopped working entirely, but it would work again after clicking the icon (which might refresh the extension) and then Alt + S to select text.
I even tried replacing the above code in \js\background\background.js which is associated with this sort of runtime error, with the following code.
It still gives some other error in js/application.js regarding the following line.
I'm not a web developer at all. Anyone with the skills to fix the errors for it to be accepted by the Store again? |
I'm on the lookout for a developer to tackle this issue. I'm not versed in JavaScript myself. |
I'm no javascript developer as well. I tried to make it work with manifest v3 but it's so damn hard. |
Reedy was AWESOME! |
@GoulartNogueira it's not abandoned. Although resources for development are very limited at the moment. We are working to restore it in all stores (Google Play, Chrome). Meanwhile, you can take the latest app or extension builds in the Telegram channel (it is an official Reedy channel): Android version is also still available in the Huawei App Store and Amazon App Store. |
Finally, Reedy Speed Reading is now back in the store! https://chromewebstore.google.com/detail/reedy-speed-reading/ihbdojmggkmjbhfflnchljfkgdhokffj?hl=en Please check it out! |
Chrome Store removed extension because of policy compliance issue.
Reedy uses 'tabs' permission for user convenience, but it's not considered as a valid reason by Google any more.
While true (almost all functions can work without this permission) such change requires additional time for development.
Any PR for this change can monstrously speed up this process!
The text was updated successfully, but these errors were encountered: