You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
unexpected message format: SyntaxError: JSON.parse: unexpected character at line 1 column 2 of the JSON data
listen WindowMessageListener.ts:46
in the dev console, over and over, at least once per second if not more. The offending line.
Definitely should not leave a console.warn in production. It's flooding my console when I'm trying to do web development, making my job harder during the day. I have to disable the extension for my development.
I don't know whether or not the message itself indicates something seriously wrong, but it's definitely not wanted. I hope the issue can be resolved by either removing the console.warn from this extension, or fixing the issue itself, of trying to parse something as JSON which is not JSON.
Expected behavior
Don't spew warnings in the user's dev console.
Steps to reproduce
Open any page.
Open the dev console.
The extension starts to spew warnings in there.
Environment
OS: Arch Linux
Browser: Firefox 122.0.1
Vimmatic version: 0.6.1
The text was updated successfully, but these errors were encountered:
Ignore unexpected message from `window.postMessage()` on the content
script. The content script can receive messages from other than the
add-on, the loaded page or other addons.
close#351
The issue is already reported or known issue?
Current behavior
This extension spews the following message:
in the dev console, over and over, at least once per second if not more. The offending line.
Definitely should not leave a
console.warn
in production. It's flooding my console when I'm trying to do web development, making my job harder during the day. I have to disable the extension for my development.I don't know whether or not the message itself indicates something seriously wrong, but it's definitely not wanted. I hope the issue can be resolved by either removing the console.warn from this extension, or fixing the issue itself, of trying to parse something as JSON which is not JSON.
Expected behavior
Don't spew warnings in the user's dev console.
Steps to reproduce
Environment
The text was updated successfully, but these errors were encountered: