Viewer plugin not loading in new tab in chrome

[dlobo]

Hi,

The latest PDF-XChange Viewer plugin (v. 2.5.0214.0001) is not working properly in the latest stable chrome (v. 32.0.1700.76 m). I'm using Windows 7. The problem is that when trying to open a pdf link in a new tab (middle click or ctrl + left click), the new tab stays black until you re-size it, then the pdf appears in the screen. Normal left click in a pdf link loads the pdf plugin correctly.

Is anybody else having this problem?

Thanks!

[Will - Tracker Supp]

Hi dlobo,

Thanks for the post - this is a known issue, but whether our own or Chrome's is not something that we're entirely sure of yet, at this point. Our Dev. Team are investigating this and we will advise further when we know more.

HTH!

[dlobo]

Will, thanks for the quick answer. I hope you guys get this sort out soon!

[Paul - Tracker Supp]

[Corwin - Tracker Sup]

Hi dlobo,

This is Chrome problem (other PDF readers are affected too)
http://code.google.com/p/chromium/issue ... ?id=333449

HTH.

[dlobo]

Yes, and it seems it will be fixed in the next version of chrome (33):

https://code.google.com/p/chromium/issu ... ?id=335900

Thanks for checking it out.

[Tracker Supp-Stefan]

[lakeskiwi]

Yes, similar problem, but I found a slightly different way of getting rid of the black screen. Try opening a second pdf on a new tab in the same instance of Chrome, and then reload either one of them, and both pages will appear.

However, I got totally fed up with this bug, and so have disabled the PDFxChange plugin within Chrome (chrome://plugins/) and also unchecked the Chrome setting for "Ask where to save each file before downloading" under "Downloads" in the Chrome settings windows.

This means each PDF now appears as a download icon in the lower left corner of the browser window, but a single click on that will open the document properly in PDFxChange and you are then free of any clash going on between Chrome and PDFxChange.

[Tracker Supp-Stefan]

Thanks for sharing your solution lakeskiwi,

Hopefully Google will fix this problem in Chrome quickly.

Regards,
Stefan