TokenizingTextBox will Place New Tokens to Wrong Side in Some Cases

[ShimizuTheLotus]

Describe the bug

In some cases, the new tokens created will be placed at the right side of the input box.

Steps to reproduce

1. Create tokens like Pic 1.
2. Press shift and then select 1st ~ 3rd like Pic 2.
3. Press backspace and type, the coltrol will looks like Pic 3 and 4.

Expected behavior

No matter how to operate, the input box will still at the right side.

Screenshots

Pic 1

Pic 2

Pic 3

Pic 4

Code Platform

• UWP
• WinAppSDK / WinUI 3
• Web Assembly (WASM)
• Android
• iOS
• MacOS
• Linux / GTK

Windows Build Number

• Windows 10 1809 (Build 17763)
• Windows 10 1903 (Build 18362)
• Windows 10 1909 (Build 18363)
• Windows 10 2004 (Build 19041)
• Windows 10 20H2 (Build 19042)
• Windows 10 21H1 (Build 19043)
• Windows 10 21H2 (Build 19044)
• Windows 10 22H2 (Build 19045)
• Windows 11 21H2 (Build 22000)
• Other (specify)

Other Windows Build number

Windows 11 23H2 (Build 22635.3139)

App minimum and target SDK version

• Windows 10, version 1809 (Build 17763)
• Windows 10, version 1903 (Build 18362)
• Windows 10, version 1909 (Build 18363)
• Windows 10, version 2004 (Build 19041)
• Windows 10, version 2104 (Build 20348)
• Windows 11, version 22H2 (Build 22000)
• Other (specify)

Other SDK version

No response

Visual Studio Version

No response

Visual Studio Build Number

No response

Device form factor

No response

Additional context

No response

Help us help you

No, I'm unable to contribute a solution.

[michael-hawker]

I was able to reproduce this, it's expected to be able replace tokens with text, but them being added to the end here after is a bit odd. Hopefully should be a simple logic issue someone could maybe pick up easily.

[AndrewKeepCoding]

Hi @michael-hawker!
I'd like to take look at this as my first good issue in this repo.

I've already cloned the repo, went through the instructions and ran the head project (WASDK) but when I do any changes (add token/remove token) to the TokeizingTextBox, I get the exception "Specified cast is not valid".

Might be related to #498 and #512. Is there any way to workaround this just to fix this issue?