Status: Unconfirmed
Owner: [email protected]
Labels: Type-Bug Pri-2 OS-All Area-Misc

New issue 5746 by alastairpatrick: Chrome does not invoke NPObject  
removeProperty callback when the JavaScript 'delete' operator is used
http://code.google.com/p/chromium/issues/detail?id=5746

Chrome Version       : 1.0.154.36
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
      Safari 3: Unknown
     Firefox 3: OK
          IE 7: OK (using COM instead of npruntime)

What steps will reproduce the problem?
1. In an npruntime plugin, create an NPObject implementing the hasProperty
and removeProperty callbacks. hasProperty should return true for  
property 'p'.
contained in the object.
2. From JavaScript, use the delete operator to attempt to delete the  
property.

var obj = plugin.createObject();
delete obj.p;

What is the expected result?
The NPObject's removeProperty callback should be called with the name of
property 'p'.

What happens instead?
The removeProperty callback is not called.

Please provide any additional information below. Attach a screenshot if
possible.

I tracked this problem down to CreateV8ObjectForNPObject in
webkit/port/bindings/v8/v8_npobject.cpp. The function creates a V8 proxy to
wrap the NPObject. However, it does not register named or indexed property
deleters. CreateV8ObjectForNPObject should register property
deleters that forward to the wrapped NPObject's removeProperty callback
function.

This bug is related: http://code.google.com/p/chromium/issues/detail?id=5743


--
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

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to