I was experiencing this intermittently in the past and I've identified the cause was not JSONView alone. After disabling all but the JSONView extension the problem was not occurring for me. I've reenabled other extensions one at a time and ultimately identified another extension (don't remember which one) that was causing the problem. In my case, I've dropped the usage of that other extension.

I was experiencing this intermittently in the past and I've identified the cause was not JSONView alone. After disabling all but the JSONView extension the problem was not occurring for me. I've reenabled other extensions one at a time and ultimately identified another extension (don't remember which one) that was causing the problem. In my case, I've dropped the usage of that other extension.

Since I am on a company-controlled version of Edge, I do not have full control over the extensions. My current extensions are these

If I re-enable JSONVIEW it breaks - if I disable it, it works fine. I cannot disable the "iswebhook" extension, so I cannot for sure say that it is not a combination of these two. I can say, however, that I noticed the new behaviour around Christmas - so it sort of fits with the new update of the extension.

I will look into having the "iswebhook" extension disabled to trouble-shoot further 😊

I was just told that the "iswebhook" extension (Lakeside Systrack Agent) was installed on our PCs in March 2023, so this extension and JSONview has been living nicely side by side for almost 9 months.

I will continue to investigate if I can disable it to confirm the root cause of SharePoint load issues.

It seems likely that removing the webRequestBlocking permission is the culprit - it works for directly viewing JSON but SharePoint must be doing something weird. Unfortunately if that's the case JSONView will cease to be after the ManifestV3 transition.

I can confirm the issue as well when using firefox 120.0.1 on linux.

Hello,

I have the same error in Edge when I open a SharePoint site. If I deactivate this extension it works again.
I think it's link to the last version of Edge.
I have problem too when I open a public link : https://cdn.ruckzuck.tools/rest/v2/getsoftwares?apikey=45820419983905&shortname=Google%20Chrome
It's now correctly format in Edge with the extension deactivate. So I think Edge directly integrate a JSON formater.

Other link for test : https://microsoftedge.github.io/Demos/json-dummy-data/256KB-min.json

I've submitted a new version of JSONView, I don't know when it'll be approved.

SharePoint must be doing something weird

I would say so - I experience this issue too with Sharepoint sites, and noticed that Sharepoint returns content type application/json for main (web) page requests. Sharing this here just in case it helps.

I get the same error:

MSEdge (Version 122.0.2365.80 (Official build) (64-bit)) returns: "There was an error parsing the JSON document. The document may not be well-formed." However, there is no error, as the developer tools shows.
Works fine in FireFox browser and Postman. Fiddler shows JSON is fine.
Sometimes works in Edge InPrivate view.
Disable JSONVIEW and everything works.

Simple repro in Azure Function that returns raw JSON.

    [Function(nameof(UploadBinary))]
    public async Task<IActionResult> UploadBinary([HttpTrigger(AuthorizationLevel.Anonymous, "get", "post", "patch")] HttpRequest req)
    {
        var mynewobj = new
        {
            Name = "foobar",
            City = "redmond"
        };
        return new JsonResult(mynewobj);

Is this still happening on the 3.0.0 version of JSONView?

I'll have a look when 3.0.0 is available from the firefox add-ons site.

I just checked and it seems ok now for me.

Cool, feel free to reopen if this re-occurs.

When using version 3.0.1, I still get an error.

There was an error parsing the JSON document. The document may not be well-formed.
unexpected character at line 1 column 1
Skip to main content
Home
Currently following the site, click to stop following

That's unfortunate. Can you provide me with a Sharepoint site I can access to test with?

That's unfortunate. Can you provide me with a Sharepoint site I can access to test with?

No, sorry. It is the company's sharepoint and I'm only a user.

OK well I'll reopen it but I can't do anything until I can see a site like this.

You could try this sharepoint site: https://fraunhofer.sharepoint.com/
I'm on Firefox 128.0 and also have the same issue.

As an intermediate solution, would it be possible to add a quickly accessible toggle to turn jsonview on and off? Right now it takes several clicks to turn it off, and a few more clicks to turn it back on.

I too have an issue with JSONView conflicting with SharePoint sites. Unfortunately I cannot provide access to any of these sites because I do not run them. However I think I do have some valuable experience to relate here.

1. It does not happen on the initial load of the site. Once it starts happening, I can use the browser dev tools to clear all stored data related to the site in order to get it to load once.
2. On subsequent sessions, once the conflict arises, all JSON transferred appears to be via XHR and delivered by the service worker.

For both of these things to be true, it seems like JSONView must be inadvertently trying to convert data the data in the content page based on an is-json indication from the background worker that is being triggered by an XHR request.

Yep that's definitely what's happening - but without a repro case I can't be sure if I've fixed it. So either I need access to a way to reproduce the issue, or someone who has that access needs to submit a fix.

Are there any cases where we do want an XHR request or a request other than the one for the content page to trigger a content re-formatting? Seems unlikely, but just curious if I need to keep this in mind while crafting a fix.

Nope, it should only trigger for main frame load, not XHRs or subframes.

I've published a version based on @dvogel's fix to all the stores. It usually takes a week or so for a new version to be reviewed and made available.