Closed bnjmnt4n closed 9 years ago
Ping @kitcambridge :)
Sorry I missed this, @d10; thanks for the ping! Dropping support sounds like a great approach. We'll need a major version bump for #65 either way, and I think it's worthwhile sacrificing a legacy version of Prototype (particularly since many of its extensions now conflict with DOM 4 and ES 6) if it means we can fall back to Firefox's native implementation.
:+1:
@kitcambridge what do you mean by a major version bump? v3.4.0?
v4.0. Granted, it's going to be interesting installing json3@4.0.0
from Bower or npm, but I think that ship has sailed.
Note: we need to modify README.md when we release 4.0.
Also (noting for posterity)...folks who still need old Prototype support can keep using 3.x. If we find bugs affecting both 3.x and 4.x, we can always backport fixes; there's no mandate to upgrade.
Prototype <= 1.6.1 support was added quite some time ago, in #8, back when many people were still using outdated versions of Prototype. However, the current Prototype version is 1.7.2 (released this year), and the toJSON bug was fixed in 1.7 (released in 2010).
However, if we intend to use a replacer function to serialise Dates (as in #65), it might be difficult to ensure that the toJSON property of Strings, Numbers, Arrays and Dates are not called. Thus, I would recommend we remove support for Prototype <= 1.6.1.
@kitcambridge what do you think?