Stop aggressively deleting trailing spaces during typing

[t4k]

Bug description

I think this add-on is the culprit in aggressive deletion of trailing spaces during typing.

Steps to reproduce

When the Thunderbird add-on is enabled and I am typing a sentence I sometimes type a space after a word, then start a new word, then backspace when I change my mind about the word. I only backspace to remove the word, intending to leave the space after the previous word, but it gets stripped as soon as it is the last character on the line. When I disable this add-on that behavior stops.

1. Type a series of words in a new message pane.
2. Backspace the last word on the line until only the space before it remains.
3. The trailing space from the previous word is stripped. Sometimes it appears in my UI as if it is there, but then when I type a new character it starts immediately after the final character of the previous word and the space is now gone. Other times I see the backspace deleting the last word character and the space before it.

Actual behavior

See above.

Expected behavior

An option to dis/en/able this behavior. Or run trailing space cleanup after a longer delay or something. It's really disruptive to typing.

Reproducibility on other systems

• Issue is reproducible in Firefox
  Note: If so, please consider switching your issue template to the general bug template.

Not tested in Firefox.

System

Operating system and version: macOS Sequoia 15.7.1
Thunderbird version: Thunderbird 143.0.1 & 144.0.1
Add-on version: Unicodify 0.8

Possible solution

Unknown.

[tdulcet]

Thanks for the bug report. I can reproduce the issue in both Thunderbird and Firefox, but only if the experimental Unicode autocorrect feature is enabled. This feature is disabled by default, so you must have enabled it at some point. If you disable the feature from the extension's options page, it should resolve the problem for you.

For clarity, the extension does not remove trailing spaces when Unicode autocorrect feature is enabled, so this is likely a recent regression with the Mozilla editor, caused as a result of how the extension detects where the user is typing. This method is found to be problematic for other reasons (see #4), so we are already working to find a better solution.

[t4k]

Glad to know there is a better solution being worked on. My whole point of using the extension is for the experimental autocorrection. I want typographical quotes.