QWebPluginInfo::isNull() return true if the QWebPluginInfo has been constructed with the default constructor.
There is no way to know if a QWebPluginInfo is valid after QWebPluginDatabase::refresh(). QWebPluginInfo::isNull() could be changed in QWebPluginInfo::isValid() and be used for the default constructor and for plugins that have become invalid.
I propose we make this class private in 4.6, it's not ready for prime time.
What are the primary concerns?
It's a pretty thin wrapper around PluginDatabase/PluginPackage, ie. we're exposing quite a few internals. This results in tricky stuff like what happens if you refresh plugins but have a QWebPluginInfo that points to one of the plugins that were removed? Now it suddenly has a dangling pointer, etc. Basically I'm worried that not all use-cases have not been thought trough (typical for API around already existing functionality), and we end up exposing bugs like this.
Add to that that this is really QWeb_Netscape_PluginDatabase, ie has nothing to do with the QWebFactoryPlugins. I tried to proxy this in, but it was a bit hairy.
OK I agree, it would be totally acceptable to make this a private API for 4.6.
I can have a look at that if you'ld like
Laszlo what is your comments on this? What are your requirements for such an API, and when do you need it?
Jakub, we have concerns regarding the API and given our current release pressure we'd like to delay this API. AFAICS Arora is not using these classes yet. Would you mind if we hold this off for a little while longer?
Created attachment 42380 [details]
Created attachment 42382 [details]
Committed r50456: <http://trac.webkit.org/changeset/50456>
Re-opening and removing dependency on Qt 4.6 API blocker. Technically this bug is still open, but with the committed patch it's not public API at the moment.
Comment on attachment 42382 [details]
Clearning review after landing.
=== Bulk closing of Qt bugs ===
If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary.
If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.