Bug 34809
| Summary: | [Qt] The QtWebkit bridge shouldn't expose deleteLater / destroyed | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Noam Rosenthal <noam> |
| Component: | WebKit Qt | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | cmarcelo, kent.hansen |
| Priority: | P2 | Keywords: | Qt, QtTriaged |
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | OS X 10.5 | ||
Noam Rosenthal
...or at least it should be possible to disable exposing them.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Kent Hansen
QtScript provides this via QObjectWrapOption::ExcludeDeleteLater. Looks like QWebFrame::addToJavaScriptWindowObject() needs another overload that takes QScriptEngine::QObjectWrapOptions :)
But first we should unify the QtWebKit bridge and the QtScript meta-object bindings; I don't feel like duplicating the options logic in the existing bridge at least.
Jocelyn Turcotte
=== 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.