The getValue and setValue are asynchronous and return promises that should be await ed or have their. However, Promises should automatically be returned and the code shouldn't just die on invocation of an asynchronous function. I'd expect this part:. To log a Promise which, according to the OP, it's not. I haven't done any testing, this is just my 30 second analysis. The failing is due to the grant none which prevents that anything is granted this was tested by me.
Then, GM. Once this incorrect grant is removed, Sxderp describes what will happen. It would be really nice if all errors from faulty code in a Greasemonkey script were to appear in the web console , the one that is show in the lower part of the page when you press shift-control-K. Currently, only some errors are shown there, alas. Others are shown only in the browser console shift-control , which is a mess. It does not finish as it should though. Data is listed below my screen shot and appears to be good.
The parse error is coming from the for each. When I take the each out, that is where the issues are after the script is processed. It does allow the script to process though. Thank you both so much for your help.
I used TamperMonkey and made the changes in the code as recommended and the script is now fully functioning! Search Support Search. Learn More. I am getting a parsing error! It worked for one game but is not working now!
Dang it. You can create a second fresh profile, run a test in it, and then remove it and switch back to your existing profile with nothing lost. You can follow Mozilla's "Managing Profiles" instructions , with screenshots and videos. For clarity, the steps are also explained here. Then: Select Create Profile Click Finish. Select the profile you just created, and select Start Firefox.
After the testing step below is complete, repeat step two, but select the original probably "default" profile, rather than creating a new one, to switch back. The point of creating a fresh profile is for it to be fresh and clean.
Unfortunately, plenty of software injects itself into Firefox globally, and can continue to cause problems even in a fresh profile. Once you've created and started your fresh profile, open Tools , Add-Ons , and check if any extensions are listed. If so, disable all of them and restart Firefox before continuing. With this fresh profile running, you should see Firefox at its completely default settings, like after the first time you ran it. First: Install Greasemonkey and restart Firefox.
Open Tools , Error Console. Is anything displayed there?
0コメント