but I can login with forks such as palemoon (which I am using now), but not with FF anymore (it worked alright one hour ago…). I eactivated ublock/umatrix etc everything, still the same failure
(off topic: why “du”? seit wann müssen wir uns alle duzen? I don’t understand why all sites of this world believe FB is the standard of interaction)
Could you please post any errors that are in the console? Someone else mentioned that their userscripts weren’t working on FF Quantum, and this might help us figure out what’s going on 
Hi, Eli
well, scripts work now (on my ff) only with stylus instead of stylish…
so, with all addons deactivated one sees that the cloudfront js are the problem
edit: I reverted to ESR, too much trouble. I’ll see later what to do about Quantum (waste of my learning time :=)
Hi @neoncube, I was posting in another thread about userscripts / greasemonkey not working in FF Quantum. Here’s the details from the web console:
@Hydroptere, thanks for the screenshot. I didn’t see anything obvious that would cause that issue, so I’m not sure exactly what the problem is.
@matteogiuseppe, Ah, I think I ran into essentially the same problem a while back when I was trying to get a userscript to run using Greasemonkey that I had been running using Tampermonkey.
Anyway, it looks like the script is unable to use jQuery, which is why it’s complaining about $ not being defined. I seem to remember that this can be caused by Greasemonkey operating in a sandboxed mode, and that I added something to the script to cause it to run in its old, non-sandboxed mode.
I wonder if Greasemonkey’s non-sandboxed mode doesn’t work in Firefox Quantum? Would you mind trying to run my Eliminate Phantom Entries or Replace Commas userscripts to see if they give you a similar error?
Hi there, I attempted to use your eliminate phantom entries script (which is great btw!) but am running into the same issues. Here’s the error log:
Per my note in the other thread, I’ll be going with tampermonkey from now on. Thanks again for the recommendation! 
Are you getting these errors when running the script with Greasemonkey or Tampermonkey?
Ya, you’re welcome Apparently the Firefox plugin architecture has been changed to be similar to Chrome’s (or something like that), so it’s probably a lot easier to port Chrome plugins, like Tampermonkey, to Firefox now (if one even needs to port them; I’ve been wondering if one could now just install Chrome plugins in Firefox now).
The errors I posted above were from running the scripts with grease monkey. (I’ve switched to tampermonkey and don’t have any errors now. Thanks!)
Okay, good to hear
