InformAction Forums

Will there be a change to this? Is there an issue in a tracker for this?

Aside from being annoying durint development, it’s most likely a bug, because someone left debugging output in a release candidate.

It’d be really great if someone removed it from the live version. It’s quickly done. ;)

[quote=barbaz post_id=104209 time=1624537910 user_id=181509]
Just to be clear, this is specifically about the Web Console (Ctrl-Shift-K), right? Not Browser Console, and not the about:debugging console for NoScript?
[/quote]

Exactly—I usually press [F12], but yes, it’s in the web inspector, the built-in developer tools, [u]not[/u] in about:debugging.

Just to be clear, this is specifically about the Web Console (Ctrl-Shift-K), right? Not Browser Console, and not the about:debugging console for NoScript?

[NoScript] Waiting for syncFetchPolicy to load... log.js:9:13
Freezing file:///C:/%23file.html DocumentFreezer.js:81:15
sendSyncMessage suspend #0/1 SyncMessage.js:224:19
Unfreezing file:///C:/%23file.html DocumentFreezer.js:97:15
sendSyncMessage finalizing SyncMessage.js:242:19
sendSyncMessage resume #0/0 - 15ms SyncMessage.js:233:19
sendSyncMessage finalizing SyncMessage.js:242:19

When I'm working in Firefox with a file:///, there is annoying debut output by NoScript, no matter the TRUSTED setting for the file: protocol:

[code][NoScript] Waiting for syncFetchPolicy to load... log.js:9:13
Freezing file:///C:/%23file.html DocumentFreezer.js:81:15
sendSyncMessage suspend #0/1 SyncMessage.js:224:19
Unfreezing file:///C:/%23file.html DocumentFreezer.js:97:15
sendSyncMessage finalizing SyncMessage.js:242:19
sendSyncMessage resume #0/0 - 15ms SyncMessage.js:233:19
sendSyncMessage finalizing SyncMessage.js:242:19[/code]

Those are obviously internal debug messages and should not be visible in normal production. I guess it's a specific file: protocol issue. At least, it should be configurable (like via about:config) and deactivated by default.