-
Notifications
You must be signed in to change notification settings - Fork 27
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 109.0.5407.1 can not use v6.0.1 #474
Comments
I found a similar problem in issues, but the solution said that it had already been adjusted. I checked and my version is indeed the latest 6.0.1, which confuses me. |
I downloaded version v5.0.7 and it works fine again. |
Could you install 6.0.1 and screenshot an error in console of service worker please (the same window where you run command above). |
@tcc-123 there is no visible an error message |
@tcc-123 we need the first error, before you insert and execute the code. It is important to figure out why extension fails initially. We need next actions to debug the problem
Your screenshot should looks like that (it's my result, your probably will have another error): |
@tcc-123 okay, it means Chrome 109 does not support an offscreen API, so we can't run custom translators and Bergamot translator. It is bad news, a chrome force developers to use ManifestV3, but their browser that released 1.5 years ago even does not support offscreen API. I will think how to make Linguist works for your use case, maybe we may disable custom translators feature for legacy chrome version, but it may takes time to hack it. For now you may use https://github.com/translate-tools/linguist/releases/tag/v5.0.17 that should work fine on your chrome. Thank you for report. It is important to know how Linguist works on different Chrome browser versions |
Ok, thank you very much. |
Hello!
I am using Windows 7, and the Chrome version is 109.0.5407.1. It can be used in 5.7.x (it seems to be this or 5.x.7), but now when I update to 6.0.1, it prompts that the background script is unavailable.
How can I solve it to make it available again? Thank you for your answer.
The text was updated successfully, but these errors were encountered: