Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug(windows): Key processing with text selection problems (legacy) #10007

Open
ermshiperete opened this issue Nov 14, 2023 · 1 comment
Open

Comments

@ermshiperete
Copy link
Contributor

ermshiperete commented Nov 14, 2023

The test cases for the Text Selection and Key Processing spec with a legacy app on Windows 10 show some limitations.

See here for the test cases and the google doc for the test results.

Keyman 16.0.142
Windows 10.0.19045
Google Chrome 119.0.6045.124

Failed tests

  1. (T02) ^⁞X the quick brown fox⁞ in doc. Typing BKSP, then A.
    Expected result: Â⁞
    Actual result: ^A⁞
  2. (T04) ^⁞X⁞ in doc. Typing A.
    Expected result: Â⁞
    Actual result: ^A⁞
  3. (T05) ^⁞X the quick brown fox⁞ in doc. Typing A.
    Expected result: Â⁞
    Actual result: ^A⁞
  4. (T07) ^⁞X⁞ in doc. Typing BKSP, BKSP.
    Expected result: foo⁞
    Actual result:
@mcdurdin
Copy link
Member

Can you add application and operating system version here? The results are likely to differ with TSF vs legacy input

@mcdurdin mcdurdin added this to the 18.0 milestone Nov 14, 2023
@ermshiperete ermshiperete changed the title bug(windows): Key processing with text selection problems bug(windows): Key processing with text selection problems (legacy) Nov 15, 2023
@mcdurdin mcdurdin modified the milestones: 18.0, A18S16 Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants