Skip to content

Releases: bhollis/jsonview

v3.0.1

19 Jun 18:21
a10aae5
Compare
Choose a tag to compare
  • Fixed a regression where floating-point numbers were truncated to integers.

3.0.0

18 Jun 17:56
bf7a463
Compare
Choose a tag to compare
  • JSONView is now compatible with Manifest V3, which is required in Chrome.
  • The JSON object is no longer available from the console via the global "data" property in Chrome, due to Manifest V3 changes.
  • Fixed JSONView in Edge, where it was conflicting with Edge's new built-in JSON viewer. If you like Edge's default viewer you can uninstall JSONView.
  • Fixed detection of "bare" object keys to more reliably follow what a JavaScript object literal would allow.

2.4.3

07 Jul 22:48
Compare
Choose a tag to compare

Fix recognizing content types like application/hal+json

2.4.2

07 Jul 22:48
0722718
Compare
Choose a tag to compare

Fix mangled encoding in Firefox

2.4.1

07 Jul 22:49
Compare
Choose a tag to compare

Fix mangled arrows

2.4.0

03 May 22:40
Compare
Choose a tag to compare
  • Preserve indentation when copying JSON.
  • The JSON object is available from the console via the global "data" property. Note: This may go away when JSONView is forced into the new Manifest V3 extension model.
  • Increased the number of content types that will be recognized as JSON.
  • Added Indonesian localization.

2.3.0

06 Jan 01:45
62428cb
Compare
Choose a tag to compare
  • Switch to a dark theme when your system is set to dark mode.

2.0.0

13 May 07:41
Compare
Choose a tag to compare
  • JSONView has been rewritten with the new WebExtension model, and is now compatible with Firefox 57+ and Google Chrome.
  • JSONView will now highlight any content type matching "application/*+json" in addition to "application/json".
  • Due to the new extension model, the ability to add "application/json" to the Accept header has been removed.
  • Removed the preference to use the built-in Firefox JSON viewer.

1.2.4

25 Jan 05:13
Compare
Choose a tag to compare
  • Fixed a case where JSON would fail to parse if a string containing a number was preceded by a quote that was preceded by a lot of escaped slashes, or occurred near another number.

1.2.3

17 Jan 00:16
Compare
Choose a tag to compare
  • Fixed a case where JSON would fail to parse if a string containing a number was preceded by a quote that was preceded by an escaped slash.