-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
Google’s built-in web translator does not work #1033
Comments
Oh dear, shame on me. I had “--ungoogled-supermium” as a start option. No wonder it didn’t work. Without this start option, Google’s built-in web translator works fine. |
Small addendum: Basically, I would prefer to use Supermium with ”--ungoogled-supermium”. Is there any way (maybe a “flag”?) to use the ungoogled option and still be able to use Google’s built-in web translator? |
Strange, it works fine for me. |
If I can allow requests for translation while ensuring no other requests are made to Google through Supermium itself (as opposed to visiting Google web pages, as is already permitted), I'll consider making a flag to allow an exception for the built-in translator. |
Hello Shane, That sounds good, or rather it’s very kind of you to consider making a flag to allow an exception for the built-in translator. In general, I’m very fond of Supermium, which “cures” just about everything annoying about Google Chrome updates. In issue #474, candrapersada gave the tip to add “disable-sync” to the --ungoogled-supermium switch for another concern. Would there be a similar addition to the --ungoogled-supermium switch for Google Chrome’s built-in translator? |
There is not much to describe. When I want to translate a website and select “Translate to [language]” by right-clicking, nothing happens. This is not due to the settings, which are identical to an Iron Secure Browser installed in parallel.
v. 126.0.6478.256 in Win10 Pro
The text was updated successfully, but these errors were encountered: