Description
Currently Chrome's auto-translation feature doesn't translate iframes. I opened a Chrome issue about this a while ago and it was immediately wontfixed. In my case I have a Scratch/JSBin type site that runs userland/untrusted code inside an iframe (which is sandboxed / cross-origin).
This site needs auto-translation more than the average website because the users on the platform are very lingually diverse, and obviously aren't e.g. 'companies' who have time to create translations for every language. Most people obviously just create their thing in their own language.
So this proposal is exciting to me as long as it's possible to make it work within iframes.
This comment:
mentions the possibility of disallowing use in iframes:
Those sites would need to coordinate among each other within the same browsing session. I think that should not be possible if we restrict to top-level navigables with no opener. (E.g. by requiring COOP.) That's a pretty strong restriction however, in particular disallowing iframed widgets, so we might want to explore other ways of loosening it when possible...
So I figured I'd create this issue to effectively 'vote for' iframe support. I don't have a well-informed opinion on how it should made possible. I think I could even "proxy" the requests to the parent frame in the worst case? But in the proxying case I'd probably have to build a full 'polyfill' within the child frame, since I'd want to make the API available in 'userland' too, without users having to learn a non-web-standard API.
Also potentially relevant RE inheritance: