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

Click event.detail maxes out at 3 in Firefox.

  • 2 odgovori
  • 1 ima ovaj problem
  • 5 views
  • Posljednji odgovor poslao FlyerKitten

more options

I'm trying to write a javascript app. I've noticed that when I am running my app in Firefox, the click event.detail will increment only up to three. If you click more than three times in a row, it reduces back to 2. This isn't a problem only in my app, but also when testing click event.detail at this page https://developer.mozilla.org/en-US/docs/Web/API/Element/click_event (they have a button towards the bottom of the page. I get the same problem, where I can only get event.detail to increment up as high as 3.) I tested this in Chrome, and Chrome does exactly what I need it to. However, our web app has to work in Firefox. Is this a bug in Firefox, or is there a different function I should use to see how many click events occurred in a row? I am using Firefox version 68.5.0esr (32-bit).

Thanks a lot!

I'm trying to write a javascript app. I've noticed that when I am running my app in Firefox, the click event.detail will increment only up to three. If you click more than three times in a row, it reduces back to 2. This isn't a problem only in my app, but also when testing click event.detail at this page https://developer.mozilla.org/en-US/docs/Web/API/Element/click_event (they have a button towards the bottom of the page. I get the same problem, where I can only get event.detail to increment up as high as 3.) I tested this in Chrome, and Chrome does exactly what I need it to. However, our web app has to work in Firefox. Is this a bug in Firefox, or is there a different function I should use to see how many click events occurred in a row? I am using Firefox version 68.5.0esr (32-bit). Thanks a lot!

All Replies (2)

more options

Right, it may be our bug 550528.

more options

Looks like that bug has been around for quite sometime. Is there an accepted workaround? I can't imagine I'm the only person with this problem after 8 years.