Some misspelled words are accepted as correct

[gruelingpine185]

Say I have a target word 'rob'. I can chord the word and Typey-type proceeds to the subsequent word. Now If I chord 'robs' instead, the entire target word gets matched, and as expected, my input does not match the target word. Therefore, I can't proceed to the next word. If I delete the word, Typey-type recognizes that as match and advances to the next word despite not having a word to match against. Note that this behavior does not occur afaik when input does not start with the target word. See the following recording.

Screen.Recording.2025-08-29.at.2.07.48.PM.mov

[didoesdigital]

Thanks for mentioning this @gruelingpine185. Have you previously seen this work correctly where pressing the steno * key to undo an overshooting word deletes it without Typey Type proceeding? I'm wondering if this is a new bug because something changed or if there's some other reason you're seeing this behaviour. Can you please also let me know what device, operating system and browser/version you're using?

[gruelingpine185]

Device: MacBook Air 2019 intel
OS: macOS
Browser: Brave (which is chromium based if it helps)
Versions: both are the latest versions. I don't have the version numbers in front of me rn.

I unboxed my steno board last night. I can't speak for how Typey type behaved before yesterday.

To my knowledge, when typing arbitrary words, Typey type behaves correctly. I can't do a quick test to see what triggers the bug right now, but when I get settled I can spend some time on it.

[didoesdigital]

Ah, welcome to steno! Welcome to Typey Type!

I haven't been able to reproduce the issue on a MacBook Air M3, 2024 in Chromium:

… and I haven't been able to reproduce the issue on a late 2013 MacBook Pro in Chrome either (no screen recording though).

What steno board, steno engine, and protocol are you using? e.g. EcoSteno, Plover, Gemini or TX Bolt protocol? MacBook laptop keyboard, Plover with Arpeggiate setting, "Keyboard" protocol?

When you undo the "robs" typo are you specifically pressing the * key on the steno board to trigger the Plover =undo command or some other key combination to trigger some other dictionary entry that has different behaviour? I don't think this would be a likely cause but it's useful to rule things out.

Lastly, can you reproduce the issue in another browser like Safari?

[gruelingpine185]

Board: The Uni v4
Engine: Plover
Protocol: Gemini PR

When you undo the "robs" typo are you specifically pressing the * key on the steno board to trigger the Plover

Yes, I am pressing the * key on the steno board.

Lastly, can you reproduce the issue in another browser like Safari?

Yes, I can. This was reproduced in both Safari and Chrome. The following is a of Safari (version info in next message).

Screen.Recording.2025-09-02.at.1.38.51.PM.mov

---

Sorry for making you wait. I was in the mountains and had no internet.

[gruelingpine185]

Software versions and board type

Steno board: Uni v4
Plover: 4.0.3
Safari: Version 18.6 (20621.3.11.11.3)
Brave:

Brave is up to date
Brave 1.81.137 (Official Build) (x86_64)
Chromium: 139.0.7258.158

Chrome:

Chrome is up to date
Version 139.0.7258.155 (Official Build) (x86_64)

[didoesdigital]

Hmm, I'm at a bit of a loss here. It's weird that overshooting ("hers") correctly stays on the current word but backspacing incorrectly progresses to the next word. Have you ever seen it fail going forward and incorrectly progress to the next word, e.g. leaving just the letter "s" typed on the next word? Have you ever seen it correctly undo and delete "hers" back to "", staying on the current word?

After vigorous testing, I've been able to reproduce the issue but only intermittently. My working theory is that there are timing issues around how fast events can fire and the JavaScript can handle them. It might happen a bit more frequently on your device because it's a little older. For now, I'm not sure what else I can do. I'll keep thinking about it though. In the meantime, it shouldn't mess with your scores much. As you get better at steno, you'll also have fewer stenotypos from extra trailing letters so it will become less of an issue over time too.

[gruelingpine185]

In my experience, whenever a word is spelled incorrectly, Typey Type will not advance to the next word automatically. It only happens when words are overshot and the user presses * and what's left is either "" or the correctly spelled word.

Surprisingly, I have never seen correct behavior from Typey Type when I've inputted an overshot word.

If the word typed is not an overshoot and is not correctly spelled, The user is not advanced to the next word. You can safely delete a part or the whole word and retype it with correct spelling to advance.