Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Learn More

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Habitual Javascript Errors in Firefox 26.0

more options

Firefox has always had problems with javascript (:js.(fill in number)), but literally in the past week whenever I got to a Facebook photo albums, Twitter photo sections, yahoo image galleries, etc...I get script errors EVERY time that hang the system for minutes on end before I'm allowed to close out the script.

Javascript is currently enabled on my system, so it's not that. And these happens whether I have the plugin turned on or off (I almost always have plugin's set to "never" unless they are absolutely necessary for what I'm doing). I've uninstalled and re-installed Firefox multiple times. My Windows Firewall also doesn't seem to be the issue. I've done things like switch the time to let the script run, and that doesn't really help anything.

What is the deal?

Firefox has always had problems with javascript (:js.(fill in number)), but literally in the past week whenever I got to a Facebook photo albums, Twitter photo sections, yahoo image galleries, etc...I get script errors EVERY time that hang the system for minutes on end before I'm allowed to close out the script. Javascript is currently enabled on my system, so it's not that. And these happens whether I have the plugin turned on or off (I almost always have plugin's set to "never" unless they are absolutely necessary for what I'm doing). I've uninstalled and re-installed Firefox multiple times. My Windows Firewall also doesn't seem to be the issue. I've done things like switch the time to let the script run, and that doesn't really help anything. What is the deal?

Alle antwoorden (1)

more options

There's so much history to this problem. It sounds as though you found that using Firefox in a new profile avoided this problem. I understand the convenience of returning to the old profile, but of course, it still has this problem and the cause it just not obvious. What if you create a new profile and import your bookmarks and test that for a day, and then start reintroducing add-ons the next day?

  1. 1
  2. 2