WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED WONTFIX
24102
Ideas for enhancements for Qt Runtime bridge
https://bugs.webkit.org/show_bug.cgi?id=24102
Summary
Ideas for enhancements for Qt Runtime bridge
Yael
Reported
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).
Attachments
Add attachment
proposed patch, testcase, etc.
Yael
Comment 1
2010-11-11 11:51:29 PST
We have a new bridge now, this does not make sense anymore. Closing the bug.
Darin Adler
Comment 2
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.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug