You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tend to always press space after every word during normal typing, or after each ngram while using this site, and after completing an ngram when the cursor automatically resets I tend to press space by default. When doing this, after the end of the last ngram, you'll incorrectly enter a space at the start of the next set. This isn't necessarily a behavior that I think should be disincentivized, so I propose disallowing space being entered if it's the first character.
The text was updated successfully, but these errors were encountered:
// but have a habit of typing the spacebar before pausing the session.
vartypedPhrase=this.typedPhrase.trimStart();
Sort of. I believe that space will start the wpm timer, so while leading spaces are stripped to check correctness and ignored in that sense, it impacts the wpm. It's also a poor/unclear UX: 1000 leading spaces is the same as 1 leading space which is the same as 0 leading spaces.
I tend to always press space after every word during normal typing, or after each ngram while using this site, and after completing an ngram when the cursor automatically resets I tend to press space by default. When doing this, after the end of the last ngram, you'll incorrectly enter a space at the start of the next set. This isn't necessarily a behavior that I think should be disincentivized, so I propose disallowing space being entered if it's the first character.
The text was updated successfully, but these errors were encountered: