Built-in page translation for Vivaldi
Chrome's built in translator is basically the only thing I use it for. I was wondering whether this feature will be available in Vivalid too. I noticed that Chromium based browsers tend not to have this feature. But then I ran into one that does (Slimjet), so I guess it's possible to have this feature. I'm wondering though: Why is this feature missing from most Chromium based browsers?
I still don't quit understand why axe a useful feature like the built in translator.
@avada It's not a question of axing the feature. The Vivaldi team have to rebuild it.
Try the Google translator as a web panel
avada last edited by
Of course that's not an analogue.
I can use the chrome website translator to have any site fully translated. Even ones that require logins.
@avada You already posted about this in the Feature Requests thread, and received some replies.
Built-in website translation
Apparently, only one person thinks it is worth voting for, which surprises me to be honest, but you need to understand that it takes time to build features.
While you're waiting use the extension suggested by Folgore101.
This is not a feature that needs to be implemented just not removed from the chromium base. (Since it's in chrome and at least one chromium based fork, it's obviously available.)
But whatever, Vivaldi can just keep removing/regressing features that are available in chrome such as this and drag&drop, that's bound to attract users...
Blackbird last edited by
This is not a feature that needs to be implemented just not removed from the chromium base. (Since it's in chrome and at least one chromium based fork, it's obviously available.) ...
Just because a "feature is available" in a rendering engine does not mean the code to make use of it exists in the user interface layer that rests on top of that engine. It merely means that a set of interface specs exist in the rendering engine that may be employed by appropriately coding the interface layer so as to employ the engine's feature - but that interface code is neither supplied by chromium nor necessarily trivial to implement so that a user can actually see and interact usefully/smoothly with the particular feature. Just because one chromium fork's developers may choose to code their interface layer to employ the translation feature does not mean other developers will see the coding effort and tradeoffs the same way for their own particular interface design.