[BUG] JSON.parse parsing error occurred in a specific website

[F9y4ng]

(Please fill out the issue template with your details)

Expected Behavior

Can get the correct JSON.parse method.

Actual Behavior

Sequence of actions:

1. Create the following script [1]
2. Visit https://ww7.manganelo.tv/
3. JSON.parse method reports error

• Chromium: 120
• TM: 5.0.1/5.0.6192 BETA
• OS: WIN10

script [1]

(Please give an example of the script if applicable.)

// ==UserScript==
// @name         New Userscript
// @namespace    http://tampermonkey.net/
// @version      2024-01-18
// @description  try to take over the world!
// @author       You
// @match        *://*/*
// @icon         data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==
// @grant        unsafeWindow
// @run-at       document-start
// ==/UserScript==

(function() {
  'use strict';
  console.log(1,JSON);
  console.log(2,JSON.stringify);
  console.log(3,JSON.parse);
})();

[F9y4ng]

I wonder if it would be better to provide a new API interface through TM extension to obtain the original methods (including window.console, window.JSON, etc.)?

[7nik]

Sandboxed window should contain only original non-modified globals anyway. This bug doesn't occur in FF.

You could workaround it with // @sandbox DOM (unless you need unsafeWindow) but it still requires allowing this mode by the user in the TM settings.

[F9y4ng]

Sandboxed window should contain only original non-modified globals anyway. This bug doesn't occur in FF.

You could workaround it with // @sandbox DOM (unless you need unsafeWindow) but it still requires allowing this mode by the user in the TM settings.

Thanks, I used GM_addElement("iframe") to get JSON.parse to temporarily solve this ISSUE.