Skip to content

Conversation

@jahorton
Copy link
Contributor

@jahorton jahorton commented Nov 21, 2025

We've now reached a point where we can finally begin to consider word-boundary correction. This could occur due to different causes:

  1. Whitespace fat-fingering - either by correcting to a whitespace key or away from it
  2. epic/dict-breaker: word boundaries are far more ambiguous for its target languages

Eventually...
3. Autocorrection due to the user fat-fingering onto a key that triggers autocorrection. As it wasn't directly and manually triggered, we should consider correcting the suggestion's acceptance, undoing it and correcting differently if later input merits it.

TODO: add specialized unit tests for the newly-supported pathways

Build-bot: skip build:web
Test-bot: skip

@keymanapp-test-bot
Copy link

keymanapp-test-bot bot commented Nov 21, 2025

User Test Results

Test specification and instructions

User tests are not required

Test Artifacts

  • Web
    • KeymanWeb Test Home - build : all tests passed (no artifacts on BuildLevel "build")

@github-actions github-actions bot added web/ web/predictive-text/ change Minor change in functionality, but not new labels Nov 21, 2025
@keymanapp-test-bot keymanapp-test-bot bot changed the title change(web): utilize and track multiple potential tokenizations of user input change(web): utilize and track multiple potential tokenizations of user input 🚂 Nov 21, 2025
@keymanapp-test-bot keymanapp-test-bot bot added this to the A19S16 milestone Nov 21, 2025
@keyman-server keyman-server modified the milestones: A19S16, A19S17 Nov 22, 2025
@keyman-server keyman-server modified the milestones: A19S17, A19S18 Dec 6, 2025
@keyman-server keyman-server modified the milestones: A19S18, A19S19 Dec 21, 2025
@keyman-server keyman-server modified the milestones: A19S19, A19S20 Jan 3, 2026
@keyman-server keyman-server modified the milestones: A19S20, A19S21 Jan 16, 2026
@keyman-server keyman-server modified the milestones: A19S21, A19S22 Jan 31, 2026
@jahorton jahorton force-pushed the refactor/web/realign-tokenization branch from 49391d5 to 3473c6f Compare February 3, 2026 14:48
@jahorton jahorton force-pushed the change/web/start-multi-tokenization branch from dead790 to e7e019d Compare February 3, 2026 15:12
@jahorton jahorton force-pushed the refactor/web/realign-tokenization branch from 3473c6f to 4f257f5 Compare February 5, 2026 19:44
…er input

We've now reached a point where we can finally begin to consider word-boundary correction.  This could occur due to different causes:
1.  Whitespace fat-fingering - either by correcting to a whitespace key or away from it
2.  epic/dict-breaker:  word boundaries are far more ambiguous for its target languages

Eventually...
3. Autocorrection _due_ to the user fat-fingering onto a key that triggers autocorrection.  As it wasn't directly and manually triggered, we should consider correcting the suggestion's acceptance, undoing it and correcting differently if later input merits it.

Build-bot: skip build:web
Test-bot: skip
@jahorton jahorton force-pushed the change/web/start-multi-tokenization branch from e7e019d to 3c2b0bf Compare February 5, 2026 19:56
@jahorton jahorton changed the base branch from refactor/web/realign-tokenization to feat/web/specialized-spurs February 6, 2026 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

change Minor change in functionality, but not new epic-autocorrect web/predictive-text/ web/

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

2 participants