Bug 34809 - [Qt] The QtWebkit bridge shouldn't expose deleteLater / destroyed
Summary: [Qt] The QtWebkit bridge shouldn't expose deleteLater / destroyed
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Qt (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords: Qt, QtTriaged
Depends on:
Blocks:
 
Reported: 2010-02-10 14:41 PST by Noam Rosenthal
Modified: 2014-02-03 03:16 PST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Noam Rosenthal 2010-02-10 14:41:20 PST
...or at least it should be possible to disable exposing them.
Comment 1 Kent Hansen 2010-03-12 08:30:16 PST
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.
Comment 2 Jocelyn Turcotte 2014-02-03 03:16:09 PST
=== 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.