-
Notifications
You must be signed in to change notification settings - Fork 33
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
is this project abandoned? #84
Comments
Hmm I'd consider it so yes. The message you got is since this extension was not (yet) migrated to manifest v3. This is a new format that requires a massive amount of changes. I did try to do some initial work on this migration to get an idea of whether it was feasible but I found it to be infeasible. There's just too many changes, especially for an extension as old as this one. It was built on some pretty ancient web technologies that have become obsolete by now and that are even less so supported. I'll keep this issue open to make it more visible to those looking for a similar explanation. |
Hi, is there any alternative if this project is not updated anymore? I can't find it anything :( |
Greasemonkey/tampermonkey is a pretty good alternative for running "userscripts". Similarly |
Thank you for answer. I would run custom scripts with selected text as parameter. |
I think you could probably make that work with greasemonkey/tampermonkey. IIRC they don't have a right-click menu entry to activate scripts but you could always write a script that listens for a specific keyboard shortcut and fires that way. Or maybe they've built in some other ways of "firing" a script at this point. |
Do you know the names of any? I have looked but can't seem to find any that have been updated to manifest v3... |
Ah yeah you're right. I did some searching too but there don't seem to be any good ones that are updated... |
is this project abandoned? when i want to download the extension from web store i got "This extension may soon no longer be supported because it doesn't follow best practices for Chrome extensions."
The text was updated successfully, but these errors were encountered: