[Webkit-unassigned] [Bug 33053] JSON.stringify and JSON.parse implementations needlessly process properties in the prototype chain

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Jan 4 02:10:53 PST 2010


--- Comment #7 from Kent Hansen <kent.hansen at nokia.com>  2010-01-04 02:10:50 PST ---
(In reply to comment #6)

Sorry, I misread the test input. b of course _is_ an "own" property.
But yeah, what's happening is, "foo" will be the last item in the
PropertyNameArray after the call to getPropertyNames(), even though the
property is not an "own" property; after the call to the "b" getter, however,
"foo" will be an own property, so it won't be rejected by the next call to
hasOwnProperty(), hence the side-effect-generated "foo" property ends up in the
Again, coming back to the spec, the propertylist is initialized before the
property values are stringified, so I believe properties added during the
stringification should not be part of the output.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list