[Webkit-unassigned] [Bug 35550] New: Allow a plugin to participate in the browser's print workflow.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Mar 1 15:24:36 PST 2010


https://bugs.webkit.org/show_bug.cgi?id=35550

           Summary: Allow a plugin to participate in the browser's print
                    workflow.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebKit API
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: sanjeevr at chromium.org
                CC: fishd at chromium.org


I am working on extending the Pepper NPAPI extensions interface to allow a
plugin to support printing. The current NPP_Print interface has a few
drawbacks. For one, the interface is platform dependent (it expects an HDC on
Windows etc). Also, it expects a full-page plugin to completely control the
print workflow (i.e. show a page setup dialog print dialog etc). This may not
be possible for plugins running in a sandbox (e.g. the Chromium sandbox).
Instead, the idea is to extend the API to allow us to query information like
number of pages to print from the plugin and have the browser put up the print
dialog (just like it would in the case of printing a web page). In addition,
the plugin would support APIs to print a specific page in a raster or a vector
format given the user-selected print settings.

To make this possible, we need to add some printing interface methods to
WebCore::Widget. In addition we need to add support in Chromium's
implementation of WebKit::WebFrame to allow us to bypass Webkit and go to the
plugin directly for printing needs (if the plugin supports the new custom print
interfaces).

I am working on making these changes and plan to submit a patch for review
soon.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list