WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
111245
Add API to allow WK2 clients to query the list of installed plug-ins.
https://bugs.webkit.org/show_bug.cgi?id=111245
Summary
Add API to allow WK2 clients to query the list of installed plug-ins.
Jer Noble
Reported
2013-03-01 23:41:03 PST
Add API to allow WK2 clients to query the list of installed plug-ins.
Attachments
Patch
(4.72 KB, patch)
2013-03-02 08:26 PST
,
Jer Noble
no flags
Details
Formatted Diff
Diff
Patch
(12.09 KB, patch)
2013-03-04 12:00 PST
,
Jer Noble
no flags
Details
Formatted Diff
Diff
Patch
(12.13 KB, patch)
2013-03-04 12:24 PST
,
Jer Noble
ap
: review+
Details
Formatted Diff
Diff
Show Obsolete
(2)
View All
Add attachment
proposed patch, testcase, etc.
Jer Noble
Comment 1
2013-03-02 08:26:45 PST
Created
attachment 191107
[details]
Patch
Jon Lee
Comment 2
2013-03-02 18:05:51 PST
<
rdar://problem/13329717
>
Maciej Stachowiak
Comment 3
2013-03-04 01:23:59 PST
Comment on
attachment 191107
[details]
Patch r=me
Alexey Proskuryakov
Comment 4
2013-03-04 09:47:37 PST
From past experience, loading plugins is known to be a very expensive operation. Shouldn't this API be asynchronous, returning the answer in a callback?
Jer Noble
Comment 5
2013-03-04 09:51:03 PST
The handling of this call occurs entirely within the UIProcess. Unless we wanted to marshal the request on another thread, what would the point of a callback be?
Brady Eidson
Comment 6
2013-03-04 09:52:22 PST
Comment on
attachment 191107
[details]
Patch Indeed. PluginInfoStore::plugins() potentially does all sorts of heavy handed i/o. I'm going to go so far as to change this to an r- until Jer can convince us it's okay to be synchronous.
Brady Eidson
Comment 7
2013-03-04 09:53:38 PST
(In reply to
comment #5
)
> The handling of this call occurs entirely within the UIProcess. Unless we wanted to marshal the request on another thread, what would the point of a callback be?
When will this new API be called? Have you explored marshaling to another thread?
Jer Noble
Comment 8
2013-03-04 12:00:56 PST
Created
attachment 191283
[details]
Patch
kov's GTK+ EWS bot
Comment 9
2013-03-04 12:06:04 PST
Comment on
attachment 191283
[details]
Patch
Attachment 191283
[details]
did not pass gtk-ews (gtk): Output:
http://webkit-commit-queue.appspot.com/results/16967063
Brady Eidson
Comment 10
2013-03-04 12:23:16 PST
Comment on
attachment 191283
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=191283&action=review
> Source/WebKit2/UIProcess/API/C/WKContext.h:52 > WKContextPlugInAutoStartOriginHashesChangedCallback plugInAutoStartOriginHashesChanged; > WKContextNetworkProcessDidCrashCallback networkProcessDidCrash; > + WKContextPlugInInformationAvailableCallback plugInInformationAvailable;
Please add a // Version 1 comment before the new callback. See WKPage.h for the loaderclient and uiclient for examples.
Jer Noble
Comment 11
2013-03-04 12:24:46 PST
Created
attachment 191289
[details]
Patch
Alexey Proskuryakov
Comment 12
2013-03-04 12:34:33 PST
Comment on
attachment 191289
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=191289&action=review
> Source/WebKit2/UIProcess/API/C/WKContext.h:56 > + WKContextPlugInInformationAvailableCallback plugInInformationAvailable;
Maybe plugInInformationBecameAvailable or plugInInformationLoaded?
> Source/WebKit2/UIProcess/Plugins/PluginInfoStore.h:41 > +class PluginInfoStoreClient {
It would be nice to put this in a separate file. PluginInfoStore.h has data and includes a client is unlikely to ever care about, yet it currently has to include the whole thing to implement PluginInfoStoreClient interface. Not such a big deal, since there is only one client that's already huge.
Jer Noble
Comment 13
2013-03-04 14:10:29 PST
Committed
r144672
: <
http://trac.webkit.org/changeset/144672
>
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug