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).
We have a new bridge now, this does not make sense anymore. Closing the bug.
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.