Google™ Translator
-
kiasari last edited by
This extension was great but with new updates I'm unable to open any PDF file so I have to disable it. please fix this bug. (It maybe Opera browser issue).
-
burnout426 Volunteer last edited by
When navigating to a pdf file, the pdf is embedded into the document with an "embed" element. You can hit ctrl + shift + I and look on the Elements tab to see this.
In the extension, in \data\content_script\inject.js, on line 208, when
mainDIV.appendChild(iFrame);
is executed, (where an iframe is appended to the div that was inserted earlier in the document), the content of the embedded document gets scribbled on by the extension. If you look at the Elements tab in the developer tools, you'll see that the embed element now has a whole document as a child node. That shouldn't be there. It must be replacing the original pdf content.Same thing happens in Chrome.
Still need to investigate more.
A simple workaround might be to just avoid the appendChild call if document.location.href contains ".pdf" or something like that. But, figuring out why appending an iframe to the document clobbers the embed's document (maybe Chromium bug/change) would be better.
-
burnout426 Volunteer last edited by
Here's a minimal test extension that I believe represents the issue when trying to view a PDF. In short, adding an iframe to the document (the document that embeds the pdf with an EMBED element when you navigate to a PDF file) via an extension, clobbers the embedded document loaded by the EMBED element.
-
burnout426 Volunteer last edited by
Goto the URL
chrome://flags/#mime-handler-view-in-cross-process-frame
and disable it. If that works, you can use that as a workaround for now. -
burnout426 Volunteer last edited by
Filed a Chromium bug at https://bugs.chromium.org/p/chromium/issues/detail?id=1046795.
-
burnout426 Volunteer last edited by
@burnout426 said in Google Translator:
Filed a Chromium bug at https://bugs.chromium.org/p/chromium/issues/detail?id=1046795.
The fix for this is in Chromium 82.0.4045.0. It might be a while before the fix reaches stable though. Until then, use can still disable this flag.
-
burnout426 Volunteer last edited by
@burnout426 said in Google Translator:
@burnout426 said in Google Translator:
Filed a Chromium bug at https://bugs.chromium.org/p/chromium/issues/detail?id=1046795.
The fix for this is in Chromium 82.0.4045.0. It might be a while before the fix reaches stable though. Until then, use can still disable this flag.
Or, you can try this modified version of the extension that tries to work around the issue for now. See the readme.txt in it for details of the fix. Download the zip file, extract it, goto the URL
opera://extensions
in Opera, turn on developer mode, click "load unpacked" and point it to the extracted folder (where manifest.json is at). -
burnout426 Volunteer last edited by
This is fixed in Opera Stable and Opera Developer now.
https://blogs.opera.com/desktop/2020/02/opera-66-0-3515-72-stable-update/
https://blogs.opera.com/desktop/2020/02/opera-68-0-3590-0-developer-update/
-
burnout426 Volunteer last edited by
Fixed in Beta now too.
https://blogs.opera.com/desktop/2020/02/opera-67-0-3575-13-beta-update/.
-
pedrowolfp2 last edited by
Why doesn't it work on google searches? This Sucks! I've been using this for a long time, but it's frustrating that it doesn't work on any site by google not just google searches.
-
leocg Moderator Volunteer last edited by
@pedrowolfp2 Because you didn't enabled it to work in search engines?
-
leocg Moderator Volunteer last edited by
@pedrowolfp2 Yes, you need to go to the extension settings and enable it for search engines.
-
pedrowolfp2 last edited by pedrowolfp2
@leocg Oh, now I see it. Has nothing to do with the extension, Sorry, and thank you.