-
Notifications
You must be signed in to change notification settings - Fork 343
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
Large amount of JS warnings causing lags #1355
Large amount of JS warnings causing lags #1355
Comments
This has been annoying me too. These days I also add the following flag to every
That will reduce the clutter. |
@Rob--W and I briefly discussed about it and we agreed that it could be reasonable to leave "javascript.options.strict" pref to its default value (which is false) and maybe document how to toggle the pref to get warning messages on the possible incorrect code (e.g. in the MDN doc pages related to web-ext) |
The `javascript.options.strict` option results in lots of log spam, which not only makes debugging harder, but also slows down Firefox. The `javascript.options.showInConsole` option was removed too because true is already the default value. Fixes mozilla#1355
The `javascript.options.strict` option results in lots of log spam, which not only makes debugging harder, but also slows down Firefox. The `javascript.options.showInConsole` option was removed too because true is already the default value. Fixes #1355
Is this a feature request or a bug?
A bug.
What is the current behavior?
It seems JS warnings are gathered from all of the scripts running on the site. This causes an overload and lags the browser. They are mostly ReferenceErrors:
How to reproduce:
web-ext run
.I've also noticed that the reload doesn't work for me, at least not for a script - I useThis works now, I didn't change anything so not sure why.console.log
in a content script.What is the expected or desired behavior?
None of such warnings - just like when I run Firefox normally.
Reload should work for JS (?).Version information (for bug reports)
The text was updated successfully, but these errors were encountered: