Open Bug 1973626 Opened 2 days ago Updated 2 days ago

Typing space does not correctly align the cursor after the space. Compatibility with Keyman and thunderbird/firefox 139.0+

Categories

(Thunderbird :: Untriaged, defect)

Thunderbird 139
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: ross_cruickshank, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36

Steps to reproduce:

Install ThunderBird v139.0.1 or greater
Install Keyman for Windows https://downloads.keyman.com/windows/stable/18.0.238/keyman-18.0.238.exe
Install the euro latin keyboard
Click on "+ New Message" in Mail
Start typing in the Body text with a Keyman keyboard

issue on git hub reported here https://github.com/keymanapp/keyman/issues/14111
Possibly related to these changes
Possibly related:

  • 1961521: In contenteditable, typing a Compose sequence after whitespace shifts it to before the whitespace
  • 1959352: WhiteSpaceVisibilityKeeper::NormalizeWhiteSpacesToSplitTextNodeAt() may not retuern proper point if it deletes the last Text of its parent
  • 1658699: [meta] Ship Blink-compat white-space normalizer
  • 1959323: HTMLEditor::InsertElementAtSelectionAsAction deletes preceding block's text when it's called after a block

Actual results:

Every time a spacebar is pressed the space is inserted after the cursor. This results in a sentance with no spaces and all the spaces at the end.
"ThisisaKeymanTest"

Expected results:

When a space is pressed the cursor postion should be after the space.
"This is a Keyman Test"

Summary: typing space does not correctly align the cursor after the space compatibility with Keyman and thunderbird/firefox 139.0+ → Typing space does not correctly align the cursor after the space. Compatibility with Keyman and thunderbird/firefox 139.0+

Thunderbird version bisecting of no space insertion. The result is as followed:
Version | Issue encountered | Notes
-- | -- | --
139.0.2 | Yes | Latest version
139.0.1 | Yes |  
139.0 | Yes | Issue started
138.0.2 | No |  
138.0.1 | No |

You need to log in before you can comment on or make changes to this bug.