From time to time, I'll come across some information (a blog post, an article etc) in another language that I'll want to translate and then add to my reading list.
I may also want to perform some other workflows like say; taking some screenshots of a page if I like the design or saving the page using an extension.
To some degree, this is not currently possible using Kagi Translate as the translated content is part of an iframe which, for a lot of extensions, is considered somewhat invisible meaning that existing workflows may not be easy to carry out, if at all.
To better understand this, I'll compare Google Translate and Kagi Translate side by side.
For this particular instance, I'm interested in this Japanese blog post about the Ricoh GR II camera, describing various camera settings.
Being a standard webpage, I can of course operate on this page using extensions but it's not particularly useful because I can't personally read Japanese.
If I throw this page into Google Translate, it translates the page and surprisingly, I can operate on the page using the right click context menu just as if it were the original page.
This is possible because Google Translate serves the header as an iframe while leaving the page content as part of the HTML body where as Kagi Translate serves the page content as an iframe with only the header being part of the HTML body.
This means I can save the article for reading later (as well as whatever other workflows)
In the case of Kagi Translate however, the page content being within an iframe means that most of the browser context menu doesn't render, probably due to general extension restrictions.
This also results some of Kagi's own building blocks (such as the Universal Summariser extension) not playing together as nicely as they could, given the translated page content can't be properly targeted.
It's also pretty crazy how wonky Google Translate seems to have become. While doing these side by side tests, Google Translate kept defaulting to Māori as the translation language.
