JSON should be handled in Adapters instead of JSON2. about history.js

[balupton]

Thanks dlee,

We actually use both JSON.parse and JSON.stringify, despite MooTools and Prototype including both of these JSON implementations - jQuery only includes JSON.parse - so we still need to include JSON2.

It's quite lightweight so I don't see the include as an issue, if it is then feel free to make a recommendation on how we can cut out the JSON code altogether - as right now it is only being used to create hashes for the objects to store - which is quite a fitting use case...

Alternatively, we could manually include the JSON.stringify code in the jQuery Adapter instead... But this would incur larger loads for browsers that natively include JSON...

Thoughts?

[balupton]

v1.5 will split the HTML4 and HTML5 functionality; so the user is able to support only the HTML5 browsers, or HTML5 and HTML4 browsers.

As such for the user who only wants to support HTML5 browsers they don't need the JSON ability (as HTML5 browsers already support it) - where including JSON in the adapters would mean they still get it.

As such, this change is rejected.