Hi jdalton, Thanks for the info!! Now I understand more to the problem and found some workaround others have done years ago. And the problem appeared in other js lib like prototype......
As with the old post said, the hasOwnProperty check is good enuf for this problem. It seemed that the workaround was rejected due to the performance degradation(well I have not done any test) as said by John Resig "Especially since the hasOwnProperty work around will add a performance hit to all object property iterations (which is unacceptable)". Now I recall that my intention to post the new fix is to minimize the performance hit to hope that the fix can get accepted, if the only reason for rejecting any backward-compatibility issues are just because of performance. Nothize On Mar 17, 10:25 pm, jdalton <[email protected]> wrote: > Hello Nothize, > > Modifying Object.prototype will cause more than problems with jQuery. > Anything that for-in iterates over an object will be affected. > > json2 follows the ECMA 3.1 draft, and uses native JSON api where > available, so its a pretty win win solution. > Trying to back in a patch for this issue seems very wrong. > > - JDD --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" 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/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
