Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

LogMeIn call for file using javascript does not work

  • 4 trả lời
  • 1 gặp vấn đề này
  • 8 lượt xem
  • Trả lời mới nhất được viết bởi 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.

Tất cả các câu trả lời (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?