Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 760303
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T15:42:04+00:00 2026-05-14T15:42:04+00:00

I am working on a pet project and am at the research stage. Quick

  • 0

I am working on a pet project and am at the research stage.

Quick summary

I am trying to intercept all form submits, onclick, and every single keydown. My library of choice is either jquery, or jquery + prototypejs. I figure I can batch up the events into a queue/stack and send it back to the server in time interval batches to keep performance relatively stable.

Concerns

Form submits and change’s would be relatively simple.. Something like

$("form :inputs").bind("change", function() { ... record event... }); 

But how to ensure I get precedence over the applications handlers as I have a habit of putting return false on a lot of my form handlers when there is a validation issue. As I understand it, that effectively stops the event in its tracks.

My project

For my smaller remote clients I will put their products onto a VPS or run it in my home data center. Currently I use a basic authentication system, given a username/password they see the website and then hopefully send me somewhat sane notes on what is broken or should be tweaked.

As a better solution, I’ve written a simple proxy web server that does the above but allows me to have one DNS entry and then depending on credentials it makes an internal request relaying headers and re-writing URLS as needed. Every single html/text or application/* request is compressed and shoved into a sqlite table so I can partially replay what they’ve done. Now I am shifting to the frontend and would like to capture clicks, keydown’s, and submits on everything on the page.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-14T15:42:04+00:00Added an answer on May 14, 2026 at 3:42 pm

    To get past the return false; issue, try working with custom events.

    // Bind custom event to all forms
    
        $('form').bind('custom_submit_event',function() {
            alert('custom submit event');
        });
    
    // Bind submit event to all forms that triggers the custom event
    
        $('form').submit(function() {
            $(this).trigger('custom_submit_event');
        });
    
    // Your regular submit event for a specific form
    
        $('#myform').submit(function() {
            // Run validation/submission code
            return false;
        });
    

    I haven’t used custom events very often, but this works for me. Don’t know why it wouldn’t work with other events as well.

    You could also assign handlers to the document. As long as you don’t hit the return false; issue, they events will bubble up to the document. Might be better (more efficient) than having the overhead of many event handlers throughout the page.

        $(document).click(function() {
            alert('click')
        })
        .keydown(function() {
            alert('keydown')
        });
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I've been working on a pet project on the weekends to learn more about
I'm currently working on a (rather large) pet project of mine , a Swing
I'm working on a basic DBMS as a pet project and planning to prototype
I'm completely new to JQuery and MVC. I'm working on a pet project that
Today I'm working on a pet project using chained function calls, and I'm curious
I am working on an update function for a pet project of mine, and
I'm currently working on a pet project and need to do C++ development on
I have a pet project I am working on that is a social concept.
Working on a pet project concerning efficiency and data and this is the mission
So I am working on a pet project where I'm storing various text files.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.