Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in webconsole #424

Open
ida opened this issue May 11, 2021 · 4 comments · May be fixed by #473
Open

Error in webconsole #424

ida opened this issue May 11, 2021 · 4 comments · May be fixed by #473

Comments

@ida
Copy link

ida commented May 11, 2021

When this add-on is enabled, every visited page shows this error in the web-inspector-console:

Error: JSON.parse: unexpected character at line 1 column 1 of the JSON data

On the right side of the error-line, where usually the file-path of the error causing script is displayed, it says undefined :(

This was particulary annoying, because I tried to debug the server-side code of the webpage, until thinking of checking browser add-ons.

@ida
Copy link
Author

ida commented May 11, 2021

This related issue suggests to ex- and import the shortkeys: #315

So I went to settings, landed on moz-extension://8a332dc9-acb9-457e-a9f1-fb8c6e82163b/options/options.html where the one and only defined shortcut (alt+q) didn't show up. Entered and saved the shortcut in these settings and the error disappears!

@ida
Copy link
Author

ida commented May 12, 2021

This is reproducible. Immediately after install the error occurs until a save action via "Preferences" is done. My guess is that the settings are stored in a json-file and that this file doesn't exist initially, thus the parsing error.

If a save-action via "Manage Extension Shortcuts" is done, the error persists. That explains why me and #315 had the error even after defining one or more shortcuts in first place.

The addon-description should point out how to define a shortcut and whether that should be done via "Preferences" or "Manage Extension Shortcuts".

@egaille
Copy link

egaille commented Jul 6, 2021

As of july 06th 2021, the problem persists. If saving a shortcut in extension parameters, the error disappears.
(my extensions are shared across all my computers, but my dev-computer does not use any shortkeys, so i had the error on my dev-computer...)

Error: JSON.parse: unexpected character at line 1 column 1 of the JSON data

@ida
Copy link
Author

ida commented Nov 25, 2021

Also relates to #338

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants