It has happened too many times now, that I have accidentally pressed Enter immediately on the opening of a cloze, causing an empty submission and an inevitable reset to 0% mastered.
On the other hand it is handy to press Enter on an empty input field, to see the correct answer if I cannot come up with any answer, but this case could probably be detected by measuring how long the cloze has been open before the press of the Enter. Or, I would not mind having to input some garbage before pressing Enter, as long as the accidental reset is prevented.
It happens to me as well once in a while. Maybe the button shouldnât do anything in the first second or so, as itâs most likely pressed by mistake.
Yes, I had been thinking of raising this one too, but I hadnât gotten around to it; Iâm glad that you did. I donât think itâs by design; the green [Submit] button is ghosted out when the entry field has a zero length (even if you enter something and then delete it, the [Submit] button returns to a ghosted out state), but the [Enter] key is still active. Itâs all too easy to hit the [Enter] key one time too often (especially when the connection is lagging a little and youâre not sure whether the first one registered) and hear that dreaded âFwoomp!â followed by the score dropping to zero and the little red âincorrectâ number incrementing.
Thanks for the feedback! Updated such that submitting a blank cloze requires Enter to be pressed 2x (in other words the first Enter on an empty cloze is ignored). Please let us know of course if you notice any issues or have any further feedback. Will handle this issue in the mobile app separately.
It just happened to me, so it is not completely fixed.
Update: It happened after I had pressed â3â for âEasyâ, so if the code only handles two successive presses of the Enter key, this might need special attention.
There shouldnât have been (though thatâs always the case with bugs ). If you notice any patterns please let us know. Weâll try reproducing in the meantime.
I think Iâd rather that it not accept a blank cloze at all. Iâve just been caught out twice in one round courtesy of an increasingly worn enter key. If the user didnât want to play the word theyâd still have the option of ignoring it or entering gibberish.
Whatever was fixed here, isnât fixed any longer.
In my Fluency Fast Track review somehow the input box lost focus (I may have bumped the track pad) so there I was happily typing away into nothing, hit [Enter] just as I looked up to see an empty input box and⌠merrnerp, wrong answer. Just to confirm it, I just hit Enter twice on the next question and⌠merrnerp, wrong answer again.
Interesting, let me see if I have any FFT to review for my next round. I just tried it on my âAllâ review, and there it is still working as expected (i.e. pressing âenterâ on the blank field doesnât do anything).
Edit: Nope, tried at various points throughout my 100 round of FFT reviews, and all still in order for me at least, even though I did encounter some strange cases where one of the accented characters (and some of the others seem to be selected on occasion, but that didnât seem to affect blank + enter behaviour either). [Actually I guess the strange accent selection was just because of accidental mouse-over perhaps, I guess I was being hyper-vigilant of any oddities]
P.S. In trying to show the strange apparent âselectionâ of accented characters (even though nothing was entered in the blank field), I noticed that others might easily verify if the âenter on an empty clozeâ is still working correctly for them through the colour of the âSubmitâ button, though I havenât verified that yet, but it appears a bit lighter than usual in the screenshot of the blank cloze to me.
Edit 2: Confirmed, @LuciusVorenusX, without needing to press âEnterâ to test it, it seems that the âSubmitâ button should be appearing differently to the slightly faded version in my screenshot for you at the moment?
Iâm not sure whether this will work, but I created a GIF image to show whatâs happening.
(It didnât⌠I got a message saying that the file was too large and that the maximum is 4,096kb⌠while the GIF was in fact only 2100kb. It suggested that I use a file sharing service to share it, of which I do not have a current one. Having typed the rest of the message though Iâm going to post it as a âhold that thoughtâ until I can get some kind of file share set up.)
I deliberately slowed waaaay down to illustrate this:
At 0:02 I click in the text box. The submit button is still pale green suggesting that itâs disabled.
At 0:04 I type the âIâ, causing the Submit button to become unghosted.
At 0:06 I hit Enter for the Submit button, which changes the button to Next.
At 0:08 I hit Enter for the Next button. Immediately after that we have the next question, which then appears with the Submit button ghosted again.
At 0:11 - and I deliberately paused and looked at the state of the Submit button before I did this - I hit Enter ONCE.
Boom, wrong âanswerâ. This is on Firefox 86.0.1 (64-bit).
). If you notice any patterns please let us know. Weâll try reproducing in the meantime.
