These methods in xpcjsid use nsIXPConnect::WrapNative rather than the XPCConvert code. For JS components this ends up making a wrappedNative around a wrappedJS. This is inconsistent. It may be that we should expose the XPCConvert routines in some safe way for use outside of xpconnect. There is still an open question about how JS components *ought* to be exposed to JS code.
fix checked in. This involved changing the nsIXPConnect methods "wrapNative" and "wrapJS" to always route through the code in xpcconvert that deals with previously wrappped and DOM objects
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.