PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Reposting: button focus question

Gravity Support Forums » Plugin Support » Gravity Forms

  1. davidjoydotnet
    Member

    I'm resposting this support question since there was no response when I first posted some days ago:

    Hi, I'm trying to change the behavior triggered by hitting the keyboard's return key on the second (and final) page of a two-page form. That second page has a "previous" and a "finalize" button (you can see a screenshot here: http://cpix.org/2012-05-04_10-56-41.snagproj.png ). Hitting return is currently interpreted as clicking the previous button, but I want it to be equivalent to clicking the "finalize" button. The previous button in that form is tabindex 7, the finalize button is tabindex 8. I've been reading posts on this forum related to tweaking the tabindices but didn't quite find a solution to this problem, or at least I wasn't able to implement it.

    Basically, I need to find a way to make it so that hitting the keyboard's return button will be interpreted by the form as the finalize button being clicked, instead of the previous button.

    Thank you for your help.

    Posted 12 years ago on Friday May 4, 2012 | Permalink

  2. Carl Hancock
    Administrator

    I'm not entirely sure how to best handle this. It would probably have to be done using jQuery. I have forwarded this to one of our developers. He's currently out of the office today with family visiting but he will hopefully get a chance to review it sometime later today or tonight.

    Posted 12 years ago on Friday May 4, 2012 | Permalink

  3. Alex Cancado
    Administrator

    This should actually be the default behavior. On my test forms, the form is submitted/finalized when I press the enter key in the last page. So there is something in your form that is causing the previous button to be activated instead. If you send me a link to your form, it might help me troubleshoot this.

    Posted 12 years ago on Monday May 7, 2012 | Permalink