Hello, I have just launched a survey, and had a user report that if they hit the tab or enter key after filling in a question on the form, they are closed out and the survey acts like it was the submit key.
Have I missed a setting?

Depending on the number and type of inputs, it is normal behaviour for browsers to submit a form when the Enter key is pressed.

While recognizing that this is standard browser behavior, have any of you explored ways of over-riding it in any of your instances of limesurvey?

Any recommendations besides the following?
stackoverflow.com/questions/585396/how-t...to-submit-a-web-form

There is a strange difference between the behaviour on a iPad and, for instance, in Chrome on Windows. On a iPad the Go button (or the Enter key if you have a BT keyboard) triggers the previous submit button. On Chrome the Enter key does a Next submit.

'Next' is preferable. How do I change that for the iPad?

I'm not sure what keyCode the "go" button returns for iPhone but from what i have read its also 13. The below script should prevent most instances of enter submitting the form. Textarea wont be affected by this.

To trigger the next button, try this.

Complete test of key:
git.framasoft.org/Shnoulle/SkeletonQuest...ster/template.js#L74

Here, i focus on enter or sumbmit, can be updated to "click".

I think default behaviour must be save but not go next ?

I´m using LS Version 2.50+ Build 160718
and I´ve just notice that the if I press "enter" in the keyboard this will do the same as pressinf button "Next"
and what is worse, the same as "Submit" buttom at the end of my survey.
How do I disable this?
I want only "Next" and "Submit" buttom to do this.
Thak you

The script above that has return false should work for you.

Or just remove the line 80 to 84

DenisChenu wrote: Or just remove the line 80 to 84

Didn´t work for FireFox and Chrome.

Bigred wrote: The script above that has return false should work for you.

Sorry if i´m asking basic questions, but i´m new in this thing
I tried to copy the script that y told, but it retirned error.
I have to write the exactly script in the css template? In which line of it?
Thank you again.

adridg wrote:

DenisChenu wrote: Or just remove the line 80 to 84

Didn´t work for FireFox and Chrome.

It's not an answer .....

Put this at top of your template.js file

Bigred01 wrote: To trigger the next button, try this.

Code:

$(document).ready(function() {
    $('input').on('keydown keypress', function(e) {       
        if(e.keyCode === 13) {
            e.preventDefault();
      $('#movenextbtn').click();
        }      
    });
});

Hello! I am working with 3.17.9 + 190731 and with the Bootswatch theme.

The code above works great for me. I copied this in "Files.js" of advanced options.

But I have a problem with the numerical questions when the following questions (also numerical) have to be hidden / shown according to conditional fork. More precisely, with some numbers when I press "enter" it goes right to the immediate next question. But for the options that I need to "skip" two or more questions these are actually "hidden" and the correct question appears below but the cursor remains on the initial question. One fact: if "tab" is pressed, the cursor effectively points to the desired question.


Is it as if the code above would be useful for "movenextbtn" and maybe when there are jumps, another command must be added?

First, I thought the problem was my misuse of the configuration condition, but the logical file shows no problem.

In the example that I attach if you put a number other than 1 in the first question and press "enter" you should skip to the last question. The other questions are effectively hidden but the cursor only jumps with the "Tab" key.

Thanks in advance,
Diego