Bug 24102 - Ideas for enhancements for Qt Runtime bridge
Summary: Ideas for enhancements for Qt Runtime bridge
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P3 Enhancement
Assignee: QtWebKit Unassigned
Keywords: Qt
Depends on: 31863
  Show dependency treegraph
Reported: 2009-02-23 13:35 PST by Yael
Modified: 2014-04-24 16:44 PDT (History)
5 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Yael 2009-02-23 13:35:07 PST
1. QObjects that are dynamically created and exposed to JavaScript are not garbage-collected, leading to potentially huge memory leaks.
2. Add support for setting JavaScript exceptions from native C++ code.
3. Add a way to call JavaScript callback functions with parameters that are QObjects being dynamically created from the C++ code.
4. QObjects that are exposed to JavaScript need access to the DOM.
5. Add a way to find out if a script was initiated by the user or not.
6. Add a way to support an object behaving both as a QObject with properties and slots and as a collection of other objects. i.e. both myobject.myslot() and myobject[i] should work.
7. Enable access to objects that are added to the window object through the main frame, from iFrames (same origin policy should still apply).
Comment 1 Yael 2010-11-11 11:51:29 PST
We have a new bridge now, this does not make sense anymore. Closing the bug.
Comment 2 Darin Adler 2014-04-24 16:44:57 PDT
Moving all JavaScriptGlue bugs to JavaScriptCore. The JavaScriptGlue framework itself is long gone. And most of the more recent bugs put in this component were put there by people who thought this was for some other aspect of “JavaScript glue” and have nothing to do with the actual original reason for the existence of this component, which was an OS-X-only framework named JavaScriptGlue.