I checked with "never-defined property of existent wrapped object".
Requested following by test extesion where CurrentServer is [xpconnect wrapped nsIMsgIncomingServer], CurrentServer.ABCDEFGHIJKLMN=true; and following exceptin was caught by try/catch(e). > Try to change never-existent property of wrapped object for bug 831664 > Exception by CurrentServer.ABCDEFGHIJKLMN=true > [Exception... "Cannot modify properties of a WrappedNative" nsresult: > "0x80570034 (NS_ERROR_XPC_CANT_MODIFY_PROP_ON_WN)" It looks for me simply a "misleading condition name". If NS_ERROR_XPC_CANT_*CREATE*_PROP_ON_WN, no problem... If such condition name, it's apparent that fault is in JS code who requestd property value change even though the property is undefined(i.e. non-existent), if "creation of property via wrapped object" is not supported. And, "why undefined is returned even though property should exist" is different problem from this bug, as seen in bug 831664. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/605513 Title: Get uncaught exception when populating a form in FireFox 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/605513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
