Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

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

Full log of all events (user actions) that took place on the web-page during the session.

  • No replies
  • 1 has this problem
  • 34 views
more options

Hello! I apologize for my accent in English. I work in Mozilla Firefox, version 3.6.24. There is a need to make a full log of events (user actions) that took place on the web-page during the session: the cursor movement and clicking the "mouse" enter any values in the text fields, change the size of HTML-elements, the acquisition of focus elements and its displacement, and so on. Question: can this task be implemented in principle, if so, please tell me the approximate direction. Was thought to act via AddEventListener(/*all_event*/, ~console.log()), but as something irrational comes out. Another idea-to act through the registration of telemetry (Event pings), but until the end of it could not yet develop - is this the right direction? I think that the problem should have a solution - after all, the browser sees events in any case, even if they do not have a handler - right? Thank you for your time and attention! Sincerely, Alexey!

Hello! I apologize for my accent in English. I work in Mozilla Firefox, version 3.6.24. There is a need to make a full log of events (user actions) that took place on the web-page during the session: the cursor movement and clicking the "mouse" enter any values in the text fields, change the size of HTML-elements, the acquisition of focus elements and its displacement, and so on. Question: can this task be implemented in principle, if so, please tell me the approximate direction. Was thought to act via AddEventListener(/*all_event*/, ~console.log()), but as something irrational comes out. Another idea-to act through the registration of telemetry (Event pings), but until the end of it could not yet develop - is this the right direction? I think that the problem should have a solution - after all, the browser sees events in any case, even if they do not have a handler - right? Thank you for your time and attention! Sincerely, Alexey!