Comment #6 on issue 24883 by verdyp: With the new Acrobat Reader 9.2, no PDF appears in old Chrome windows http://code.google.com/p/chromium/issues/detail?id=24883
Resizing the window does not work for me. In fact the Adobe plugin is effectively loaded (as seen in the Javascript console), and it effectively runs in the background (you'll see that in the process explorer). The plugin effectively downloads the PDF (in its own local cache). The plugin correctly sets the mouse cursor. However it fails to display its rendering within the window provided by Chrome. It looks like if the window area offered by Chrome is clipped off (most prably by an event that is normally used to clear the window background and invalidate the window's client area and to which Chrome should reply by sending a refresh event to the plugin), and Adobe Reader can't render anything in that area, or if it renders it, it's within an empty area. The only way that works to display the PDF for me is to open the PDF in its own tab, then close Chrome completely, and reopening it, so that the previously tabs that were open will be restored with its content. But any further attempts to close the tab and reopen it to display a new PDF will continue to fail. Pressing F5 when the Adobe plugin should be displayed in the window just clears the window background to dark gray. So something is wrong in the display model or architecture for plugins in Chrome (in fast I have observed that it also affects some other plugins based on the Mozilla plugin architecture, like Adobe Reader itself). It looks like that the Adobe Reader 9.2 plugin was updated for Firefox, possibly to implement a more strict security mechanism (with better isolation from the rest of the web page), but this does not work within the HTML <embed> element that Chrome uses internally to render the plugin). May be Chrome does not properly sets the container's element size, and Adobe Reader thinks that the container area is empty or fully invisible, or Adobe Reader first checks that the element itself is within a visible window, with the standard decorations, to make sure that no site will attempt to emulate a Windows alert by displaying it in an unframed window. Or may be Adobe reader no longer accepts to render in an element of a HTML page that is not the root element of the document, or whose parent window is not a visible window (this is the trick that Chrome uses to render things offscreen within separate processes that communicate with the browser by transfering the graphics to the browser's GUI process). May be Adobe also rejects the attempt made by Chrome to copy the rendered content of the invisible area to another process like the Chrome's GUI process. There are various things to check. But the "solutions" currently proposed by Google do not work: uninstalling both Chrome and Adobe Reader then reinstalling Chrome and then Adobe Reader (last update 9.2) does not work. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
