WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
87963
Need special-case toJS(IDBAny) for IDBCursorWithValue
https://bugs.webkit.org/show_bug.cgi?id=87963
Summary
Need special-case toJS(IDBAny) for IDBCursorWithValue
Charles Wei
Reported
2012-05-31 05:40:24 PDT
For JSC binding for JavaScript IDL files, say, Base and Derived where Derived derives from Base, the JSC binding generator generates native to JS binding toJS(native object) for the base interface but not the derived interface. So "JSValue toJS(A*)" will be generated but not" JSValue toJS(B*)". with IndexedDB support, IDBAny is the wildcard interface that can be many things, like IDBRequest, IDBIndex, IDBCursor, IDBCursorWithValue. toJS(IDBAny*) generates corresponding JSValue according to the real data it holds. case IDBAny::IDBCursorType: return toJS(exec, globalObject, idbAny->idbCursor()); case IDBAny::IDBCursorWithValueType: return toJS(exec, globalObject, idbAny->idbCursorWithValue()); Actually generates both to IDBCursor objects, because there's no toJS(exec, globalObject, IDBCursorWithValue*) generated by the code generator because IDBCursorWithValue interface is derived from IDBCursor interface. So when the IDBCursor JSObject is generated for IDBCursorWithValue, it can't access the attributes (the value) hold by the actual IDBCursorWithValue object.
Attachments
Patch
(1.86 KB, patch)
2012-05-31 17:59 PDT
,
Charles Wei
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Charles Wei
Comment 1
2012-05-31 17:59:22 PDT
Created
attachment 145183
[details]
Patch
WebKit Review Bot
Comment 2
2012-06-05 22:37:44 PDT
Comment on
attachment 145183
[details]
Patch Clearing flags on attachment: 145183 Committed
r119561
: <
http://trac.webkit.org/changeset/119561
>
WebKit Review Bot
Comment 3
2012-06-05 22:37:49 PDT
All reviewed patches have been landed. Closing bug.
Darin Adler
Comment 4
2014-04-24 16:45:33 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