This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

LogMeIn call for file using javascript does not work

  • 4 antwoorde
  • 1 het hierdie probleem
  • 3 views
  • Laaste antwoord deur RealGomer

more options

We use LogMeIn Pro for remote access to our office computers. When one selects Remote Control, LMI uses javascript to call the LogMeIn client. Except in Firefox. It works perfectly well in Chrome, IE 11, and Edge. It USED to work in Firefox. What gives? What next? Javascript is enabled.

We use LogMeIn Pro for remote access to our office computers. When one selects Remote Control, LMI uses javascript to call the LogMeIn client. Except in Firefox. It works perfectly well in Chrome, IE 11, and Edge. It USED to work in Firefox. What gives? What next? Javascript is enabled.

All Replies (4)

more options

If you are getting a message about Javascript being disabled, it sounds like may Firefox's builtin Enhanced Tracking Protection (ETP) feature might be blocking some of the Javascript because it's detected as tracking code. You can try disabling ETP on the website that you are trying to use to see if that helps.

more options

How does one do that?

more options

When you are on the website you are having issues with, there's a shield icon in the left side of your address bar. Click on it and turn the toggle switch off.

See the Enhanced Tracking Protection in Firefox for desktop for more information.

more options

No good. Clicked on shield , reloaded site and still no access. The lower left corner shows "javascript: void(0)". Mozilla hiring ex-microsoft coders who destroy functions and call them new features? Or does Mozilla want me to switch to Chrome after using Firefox since it was a pup?