Comment #20 on issue 3285 by f...@chromium.org: NPConstructFunctionPtr not working correctly in NPRuntime implementation http://code.google.com/p/chromium/issues/detail?id=3285
I have a work-around of the problem: In V8, I changed it to allow things like: var a = new npobject(...); npobject is a NPObject, not a function. In the binding code, if npobject has invokeDefault, it calls invokeDefault, otherwise, it it has 'construct', it calls construct. The drawback is that the code might be confused if the npobject implements both NPN_InvokeDefault and NPN_Construct. That's said: var x = new npobject(); and var x = npobject(); are treated the same if npobject implements NPN_InvokeDefault and or NPN_Construct. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
