Correcting certain strokes while connected to Plover causes input to jump to beginning of document

[Codebreakerblue]

While connected to Plover with translations enabled, certain strokes cause the input to jump to the beginning of the document, output part of the stroke, and jump back at the next stroke. For example, stroking burial PWU/REU/A*L with the misstroke and correction AL/*/A*L outputs PWU -> bury -> bury al -> bury -> ial bury.

Windows 10, AlleyCAT 0.4.3

Steps to reproduce:

1. Open a new document in AlleyCAT.
2. Connect to Plover and enable translations.
3. Stroke PWU/REU/AL/*/A*L. (The stroke might be different, as I'm using Aerick's Lapwing dictionaries.)
4. You should see ial bury.

The stroke that outputs "ial" actually appears at the top of AlleyCAT's paper tape.

This does not happen with:

• PWR*EU/KWRAL burial
• TROR/KWRAOEUZ terrorize
• PWU/REU/KWRAOEUZ buryize
• PWU/REU/KWRAEUT buryiate
• TROR/A*L terroral
• TER/TOER/A*L territorial
  (each stroked with AL/* before the last stroke)

It does occur with:

• TER/TOER/KWRAL (TER/TOER/AL/*/KWRAL)

alleycat.bug.001.mp4