chore(windows): test ldml_test on windows

[srl295]

It seemed like this test broke in VSCode ,although the ABC+8 test passed.

    <test name="key-8-osage">
      <startContext to="𐓏" />
      <keystroke key="8" />
      <check result="8:ctxt:OK" />
    </test>

https://github.com/keyman-keyboards/ldml_test and also in-repo

[srl295]

I tested using testhost on windows 11 (x64 debug), and all passed EXCEPT:

• 8:ctxt:OK (the ABC context)
• 𐓏8:ctxt:FAIL (non-BMP context - as reported in this issue)
• 𐒻𐒷8:ctxt:FAIL (split non-BMP context)

[srl295]

I also notice in VSCode that if i click after ABC and press 8 the test fails, but if I type ABC and then press 8 it works.

Does that mean VSCode is 'non compliant'?

[srl295]

OK, testhost also fails if you click next to ABC and type 8.

ABC8:ctxt:FAIL

I'll see if I can debug it.. no, i'll need some help..

[mcdurdin]

OK, testhost also fails if you click next to ABC and type 8.

ABC8:ctxt:FAIL

I'll see if I can debug it.. no, i'll need some help..

Shall we setup a rubber ducky session? I'll ping you on Slack

[srl295]

(copyback from slack:

• vscode is noncompliant
• testhost is noncompliant
  Maybe WAD

[rc-swag]

• testhost is noncompliant
  Maybe WAD

Yes correct in non-compliant app the context is going to empty as you have pasted the text and not typed it therefore is working as expected.
Update the test markdown to specify this test requires a compliant app, then we can close this issue?

[mcdurdin]

We should add a RICHEDIT (4.0+) to testhost, so we can do both compliant and non-compliant tests

[srl295]

Update the test to specify

OK, I'll update the test source. It's not a formal test, the only 'call to action' was this issue, when I had noticed that VSCode was being seemingly erratic

We should add a RICHEDIT (4.0+) to testhost, so we can do both compliant and non-compliant tests

Need an issue for that?

[mcdurdin]

Issue opened

[rc-swag]

Ok issue opened by Marc I have assigned to me for 19.0 let's close this.