Chrome Version : 184.108.40.206 (Official Build 31086)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Firefox 3.x: OK (both NPAPI and XPCOM)
IE 7: OK (as an ActiveX control)
What steps will reproduce the problem?
Reproduction is complicated, contact me at email@example.com for details
What is the expected result?
The same JS object passed multiple times into an NPAPI plugin should
maintain identity, ie the same NPObject should be received each time.
What happens instead?
Each call with the same object passes a new NPObject instance. Even
looking into the NPObject private data, the address of npobject_ptr_ isn't
Please provide any additional information below. Attach a screenshot if
This is for a Chrome extension for the GWT DevMode plugin, which allows
debugging of GWT apps in Chrome. The current solution requires adding a
property to every JS object ever passed to Java to store a unique
identifier, but this has a few probelms:
- JS code can mangle the property, clone it between different JS objects,
or be confused by its presence
- Accessing the property from the NPAPI plugin on every call to Java for
every JS object is passed to Java is very slow, since this results in
an RPC call. Using Chrome for GWT development is roughly twice as slow
as using Firefox presently, and a significant part of this slowdown is
having to lookup object ids.