Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Támogatás keresése

Kerülje el a támogatási csalásokat. Sosem kérjük arra, hogy hívjon fel egy telefonszámot vagy osszon meg személyes információkat. Jelentse a gyanús tevékenységeket a „Visszaélés bejelentése” lehetőséggel.

További tudnivalók

A témacsoportot lezárták és archiválták. Tegyen fel új kérdést, ha segítségre van szüksége.

LogMeIn call for file using javascript does not work

  • 4 válasz
  • 1 embernek van ilyen problémája
  • 8 megtekintés
  • Utolsó üzenet ettől: 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.

Összes válasz (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?