Bug 77902 - NPP_Print is never called on Print, but NPP_SetWindow is with surprising parameters
Summary: NPP_Print is never called on Print, but NPP_SetWindow is with surprising para...
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: Plug-ins (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.6
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-06 14:28 PST by Rudi Sherry
Modified: 2022-07-01 11:35 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rudi Sherry 2012-02-06 14:28:20 PST
I am seeing no calls to NPP_Print when printing.  I am using the WebKit nightly from about a month ago, but we are also seeing this in Safari 5.1.2, both on 10.6 and 10.7.

When the user is in a document controlled by a plug-in and chooses "Print", the plugin gets the call NPP_SetWindow() with page-size window... that causes us to resize our view to be page ratio, which is surprising our users.

The Print sheet appears, then printing doesn't print anything of our content.  Then we get another NPP_SetWindow() that restores us to the Safari window size.

NPP_Print() is never called.

We are using the Cocoa Event model and the Core Animation drawing model.
Comment 1 Alexey Proskuryakov 2012-02-07 10:05:27 PST
What do you expect to be passed as printInfo->print.embedPrint.platformPrint?
Comment 2 Rudi Sherry 2012-02-07 11:40:15 PST
(In reply to comment #1)
> What do you expect to be passed as printInfo->print.embedPrint.platformPrint?

I think it would depend on the negotiated drawing model.

If we've negotiated a CoreAnimation layer, I would expect a CALayer. I can put whatever I want on that layer and return.  I would not expect it to be the same layer I provided to the browser, since that is being used to display on the window.  The browser would own the printed layer.

I'm not familiar enough with the other drawing models to know, but I expect it would be similar.
Comment 3 Alexey Proskuryakov 2022-07-01 11:35:48 PDT
Mass closing plug-in bugs, as plug-in support has been removed from WebKit.

Please comment and/or reopen if this still affects WebKit in some way.