Keyman for Web Acceptance Test Procedures

For this test run, please refer to the builds posted on https://github.com/keymanapp/keyman/pull/8560#issuecomment-1492750092.

As the feature branch has relocated test page resources, note that the links contained herein are updated to point to their new locations. A few extra tests have also been added.

Once the feature-branch lands, updating the regression test spec to use the links from this one will resolve #9023 moving forward. Some of the links may not work on master, though, hence my hesitancy to update them at the moment.

I have dropped SUITE_INSPECT for this run, as it's not against an official release of Keyman, but the rest of these tests should otherwise match what is seen at https://github.com/keymanapp/keyman/wiki/Platform-Acceptance-Test-for-Web at this time.

User Testing

SUITE_DESKTOP: Desktop Platforms

Ensure that all tests in the selections below are run on a representative set of the following browsers and setups:

GROUP_WINDOWS_FIREFOX
GROUP_WINDOWS_CHROME
GROUP_MACOS_SAFARI
GROUP_MACOS_CHROME
GROUP_MACOS_FIREFOX
GROUP_LINUX_FIREFOX

Baseline Tests

From the testing index page, use the first link ("View Keymanweb use samples") and then select "Example 1" for the following tests.

TEST_BASELINE_ADD_SIL_IPA: Using the "Add a keyboard by keyboard name" section, add sil_ipa.
- Ensure the key sequence n> produces ŋ.
TEST_BASELINE_ADD_KM: Using the "Add a keyboard by BCP-47 language code" section, add km. A Khmer keyboard should be added (perhaps khmer_basic, but not necessarily).
TEST_BASELINE_ADD_KHMER_ANGKOR: Using the "Add a keyboard by keyboard name" section, add khmer_angkor.
- Ensure the key combination Ctrl+AltB produces ឞ. Delete the character again.
- Type the following (US) keys in sequence: s u j r k. You should see ស្រុក.
- Continuing from the last test, hit Backspace, checking each time to ensure the output is as expected. As this is a reorder (keyboard) rule test, you should see:
- ស្រុ
- ស្រ
- ស្
- ស
- empty text area.
TEST_BASELINE_ADD_SPANISH: Using the "Add a keyboard by language name(s) section", add spanish. Verify that a Spanish keyboard is added to the list.
TEST_BASELINE_SWEDISH: Swap to the Swedish keyboard.
- Ensure the key sequence ' e produces é and that o \ e produces œ.

Text Selection Tests

These tests are all run with the web_context_tests keyboard on the Test unminified Keymanweb test page. They should be run on both INPUT and TEXTAREA elements. Press Ctrl+F5 to reload the page between tests.

TEST_SELECTION: Type abcx. Select bc and type q. The output after the final key should be aqx. (This is testing selection replacement with no matching keyboard rule.)
TEST_SELECTION_2: Type abcx. Select bc and type p. The output after the final key should be aqx. (This is testing selection replacement with a matching keyboard rule.)
TEST_CONTEXT_BASE: Type abcd. The output after the final key should be !.
TEST_CONTEXT_SELECTION: Type abcx. Select the x character, and type d. The output after the final key should be abcd.
TEST_CONTEXT_SELECTION_2: Type abcx. Select the x character, and delete it with Backspace. Type d. The output after the final key should be !.
TEST_CONTEXT_SELECTION_3: Type abcx. Select the x character, and type y. Press Backspace, and type d. The output after the final key should be !.
TEST_CONTEXT_SELECTION_4: Type xabcx. Select the abc characters, and type d. The output after the final key should be xdx.
TEST_SELECTION_SHIFT: (new) Type abcx. Select bc and then press the left Shift key on the OSK. The output after pressing shift should be abcx, with bc still selected.
TEST_TYPING_AUTOSCROLL: (new) Type a very long string of text into the "input field" element using the "English - English" keyboard until the text reaches its right-hand side.
- Type three additional letters.
- Verify that the text is automatically scrolled so that the last three characters and the caret (the thin, blinking | mark for text position) are visible.

Element Attachment Tests

TEST_ATTACHMENT_API: Utilize the Attachment/Enablement API functionality samples page to test the following:
- 'auto' attachment mode properly and automatically attaches to each dynamically-added control.
- 'manual' attachment mode results in a page with no KMW-activated controls.
- Each 'attached' control functions as expected for the keyboard(s) selected.
- KeymanWeb properly attaches to and detaches from each relevant type of control with the page's API-interface controls.
- Confirm that the independent-keyboard management API functions correctly.

Site-based tests of attachment API

All behavior exhibited here should feel "normal". These tests are solely to ensure that nothing got accidentally broken.

For each of these, make use of the Attachment/Enablement API functionality test page.

TEST_NORMAL_USE: Ensure that the keyboard displays and works correctly when first loaded up.
1. Click the "Create Inputs" button one time.
2. Click / touch the new page element. The OSK should display.
3. Use the OSK to type one or two keys. The keys should produce their expected output.
4. Click / touch a blank area of the page. The OSK should automatically hide.
TEST_ELEMENT_HOPPING:
1. Click the "Create Inputs" button one time and the "Create Textarea" button one time.
2. Click / touch the first of the new page elements. The OSK should display.
3. Click / touch the other page element. The OSK should remain visible.
4. Click / tough the first element again. The OSK should remain visible.
5. Click / touch a blank area of the page. The OSK should automatically hide.
TEST_SPECIFIC_KEYBOARDS:
1. Click the "Create Inputs" button three times.
2. Click / touch Dynamic area #0.
3. Click the element's "Set to Dzongkha" button.
4. Change the keyboard to French.
5. Click Dynamic area #1's "Set to Dzongkha button.
6. Click Dynamic area #1. The Dzongkha keyboard should be displayed.
7. Click Dynamic area #2.
8. Change the keyboard to Lao.
9. Click Dynamic area #0. The French keyboard should be displayed.
10. Click Dynamic area #2. The Lao keyboard should be displayed.
11. Click Dynamic area #1. The Dzongkha keyboard should be displayed.
12. Click Dynamic area #0's "Clear Keyboard" button.
13. Click Dynamic area #0. The Lao keyboard should be displayed.

Tests CJK keyboard functionality

Use the standard Test unminified Keymanweb test page.

TEST_JAPANESE_TYPING: Verify that a CJK keyboard still works.
1. Under "Add a keyboard by keyboard name", type japanese, then click Add.
2. Select the Japanese keyboard. The OSK should change shape notably:
1. Type a. A "picker" displaying a few options should display:
1. Type 2. The second option should replace the context.
TEST_JAPANESE_FOCUS: Verify that a CJK keyboard is shown and hidden properly without interfering with a page's UX.
1. Select the page's textarea element. The OSK's title bar should appear (as with step 2 for the _TYPING test).
2. Click a blank area on the page. The OSK should automatically hide and the caret should disappear from the textarea.
  - Just in case, "caret": the blinking vertical line segment that lets you know where new characters will appear in the context.
3. Select the page's input field (the second editable control). The OSK should reappear under the newly-selected control.
4. Select the page's textarea element again. The OSK should remain visible, and the caret should move from the input control to the textarea control.

SUITE_TOUCH: Touch platform tests

Ensure that all tests in the selections below are run on a representative set of the following browsers and setups:

GROUP_ANDROID_CHROME_TOUCH
GROUP_ANDROID_CHROME_HARDWARE
GROUP_IPHONE_SAFARI_TOUCH
GROUP_IPHONE_SAFARI_HARDWARE
GROUP_IPAD_SAFARI_TOUCH
GROUP_IPAD_SAFARI_HARDWARE

Baseline Tests

From the testing index page, use the first link ("View Keymanweb use samples") and then select "Example 1" for the following tests.

TEST_BASELINE_ADD_SIL_IPA: Using the "Add a keyboard by keyboard name" section, add sil_ipa.
- For physical devices, ensure the key sequence n> produces ŋ.
- For touch devices, ŋ should be a subkey of n - ensure it works.
TEST_BASELINE_ADD_KM: Using the "Add a keyboard by BCP-47 language code" section, add km. A Khmer keyboard should be added (perhaps khmer_basic, but not necessarily).
TEST_BASELINE_ADD_KHMER_ANGKOR: Using the "Add a keyboard by keyboard name" section, add khmer_angkor.
- If using a physical keyboard, ensure the key combination Ctrl+AltB produces ឞ. Delete the character again.
- If the keyboard has four rows (phone form-factor): Type in the following sequence on touch: ស ុ ្រ (subkey of រ) ក. You should see ស្រុក.
- If the keyboard has five rows (tablet form-factor): s u j r k. You should see ស្រុក.
  - If the number of rows shown does not match the type of device you're using, fail the test for this.
- Continuing from the last test, hit Backspace, checking each time to ensure the output is as expected. As this is a reorder (keyboard) rule test, you should see:
- ស្រុ
- ស្រ
- ស
- empty text area.
TEST_BASELINE_ADD_SPANISH: Using the "Add a keyboard by language name(s) section", add spanish. Verify that a Spanish keyboard is added to the list.
TEST_BASELINE_SWEDISH: Swap to the Swedish keyboard.
- If using a physical keyboard, ensure the key sequence ' e produces é and that o \ e produces œ.
- If using a touch-based keyboard, use long-press . to output ' and then press e. The two characters should not combine.
- If using a touch-based keyboard, ensure that long-press p and long-press G displays properly and that the subkeys produce the expected output.
TEST_BASELINE_CAMEROON: If using a touch-based keyboard, add the following keyboard by name: "sil_cameroon_qwerty"
- Ensure the top two rows of the symbol layer work correctly. (These have unusual 'layer' settings.)
- Ensure that the tri-color key (on both 'default' and 'shift' layers) changes layer appropriately and that keys pressed automatically transition back to the default layer. (The 'default' layer's variant is very unusual, as it matches a keyboard rule and changes layer, but doesn't generate direct output!)
- Test that a subkey on the 'default' and on the 'shift' layers output the expected character.
TEST_BASELINE_AUTOSCROLL: (new) Type a very long string of text into the "input field" element using the "English - English" keyboard until the text reaches its right-hand side.
- Type three additional letters.
- Verify that the text is automatically scrolled so that the last three characters and the caret (the thin, blinking | mark for text position) are visible.
- Verify that the keyboard does not disappear at any point while typing and that it is still visible.
TEST_ROTATION: (new) Put the test device into 'portrait' orientation - with the longer dimension held vertically.
- Type a into the input field.
- Rotate your device to a landscape (horizontal) orientation.
- Verify that the OSK repositions itself at the bottom of the screen and occupies the full width of the device.
- Rotate the device back to a portrait (vertical) orientation.
- Again, verify that the OSK repositions itself at the bottom of the screen and occupies the full width of the device.
  - After rotation, it is possible that the previously-typed 'a' will not be visible.
  - If so, please create a separate issue for this, but do not fail the test. (It appears to be a 16.0 issue, too.)

Element Attachment Tests

TEST_ATTACHMENT_API: Utilize the Attachment/Enablement API functionality test page to test the following:
- 'auto' attachment mode properly and automatically attaches to each dynamically-added control.
- 'manual' attachment mode results in a page with no KMW-activated controls.
- Each 'attached' control functions as expected for the keyboard(s) selected.
- KeymanWeb properly attaches to and detaches from each relevant type of control with the page's API-interface controls.
- Confirm that the independent-keyboard management API functions correctly.

Site-based tests of attachment API

All behavior exhibited here should feel "normal". These tests are solely to ensure that nothing got accidentally broken.

For each of these, make use of the Attachment/Enablement API functionality test page.

TEST_NORMAL_USE: Ensure that the keyboard displays and works correctly when first loaded up.
1. Click the "Create Inputs" button one time.
2. Click / touch the new page element. The OSK should display.
3. Use the OSK to type one or two keys. The keys should produce their expected output.
4. Click / touch a blank area of the page. The OSK should automatically hide.
TEST_ELEMENT_HOPPING:
1. Click the "Create Inputs" button one time and the "Create Textarea" button one time.
2. Click / touch the first of the new page elements. The OSK should display.
3. Click / touch the other page element. The OSK should remain visible.
4. Click / tough the first element again. The OSK should remain visible.
5. Click / touch a blank area of the page. The OSK should automatically hide.
TEST_SPECIFIC_KEYBOARDS:
1. Click the "Create Inputs" button three times.
2. Click / touch Dynamic area #0.
3. Click the element's "Set to Dzongkha" button.
4. Change the keyboard to French.
5. Click Dynamic area #1's "Set to Dzongkha button.
6. Click Dynamic area #1. The Dzongkha keyboard should be displayed.
7. Click Dynamic area #2.
8. Change the keyboard to Lao.
9. Click Dynamic area #0. The French keyboard should be displayed.
10. Click Dynamic area #2. The Lao keyboard should be displayed.
11. Click Dynamic area #1. The Dzongkha keyboard should be displayed.
12. Click Dynamic area #0's "Clear Keyboard" button.
13. Click Dynamic area #0. The Lao keyboard should be displayed.

User Test Results

Test specification and instructions

✅ SUITE_DESKTOP: Desktop Platforms

120 tests in 6 groups PASSED

* ✅ GROUP_WINDOWS_FIREFOX:

20 tests PASSED

- ✅ **TEST_BASELINE_ADD_SIL_IPA ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598540564))**: Verified that the key sequence n> produced ŋ. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598540564)) - ✅ **TEST_BASELINE_ADD_KM ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598540564))**: Verified that the Khmer_Basic keyboard was added. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598540564)) - ✅ **TEST_BASELINE_ADD_KHMER_ANGKOR ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598540564))**: Verified that the Khmer_angkor keyboard was added. Able to see ស្រុក by typing key sequence s u j r k. Able to see that the reorder rule test, by hitting Backspace key. - ✅ **TEST_BASELINE_ADD_SPANISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598540564))**: Verified that the Spanish keyboard was added to the list. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598540564)) - ✅ **TEST_BASELINE_SWEDISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598540564))**: Verified that the given key sequences shows the expected output. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598540564)) - ✅ **TEST_SELECTION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600540967))**: Tested in unminified Keymanweb test page and tested in both INPUT and TEXTAREA elements and here is my observations: 1. Verified that the output shows aqx. - ✅ **TEST_SELECTION_2 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600540967))**: Verified that the output after the final key shows aqx. - ✅ **TEST_CONTEXT_BASE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600540967))**: Verified that the output finally shows !. - ✅ **TEST_CONTEXT_SELECTION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600540967))**: Verified that the output shows abcd. - ✅ **TEST_CONTEXT_SELECTION_2 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600540967))**: Verified that the final key shows !. - ✅ **TEST_CONTEXT_SELECTION_3 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600540967))**: Verified that the final key shows !. - ✅ **TEST_CONTEXT_SELECTION_4 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600540967))**: Verified that the final key shows xdx. - ✅ **TEST_SELECTION_SHIFT ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600540967))**: Verified that the pressing shift shows abcx with bc still selected. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600540967)) - ✅ **TEST_TYPING_AUTOSCROLL ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602185878))**: Retested as per Josh's suggestion and here my observation: 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field. - ✅ **TEST_ATTACHMENT_API ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600642018))**: 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly. - ✅ **TEST_NORMAL_USE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600642018))**: Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up. - ✅ **TEST_ELEMENT_HOPPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600642018))**: Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area. - ✅ **TEST_SPECIFIC_KEYBOARDS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600642018))**: Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine. - ✅ **TEST_JAPANESE_TYPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600642018))**: 1. Able to add japanese keyboard. 2. Able to select the second option to replace the existing context. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600642018)) - ✅ **TEST_JAPANESE_FOCUS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600642018))**: 1. Verified that it is possible to see the japanese keyboard when I clicked either in text area or the input field. 2. If I clicked in the black area on the page, the keyboard disappeared. Seems to be working fine. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600642018))

* ✅ GROUP_WINDOWS_CHROME:

20 tests PASSED

- ✅ **TEST_BASELINE_ADD_SIL_IPA ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598608540))**: Verified that the key sequence n> produced ŋ. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598608540)) - ✅ **TEST_BASELINE_ADD_KM ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598608540))**: Verified that the Khmer_Basic keyboard was added. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598608540)) - ✅ **TEST_BASELINE_ADD_KHMER_ANGKOR ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598608540))**: Verified that the Khmer_angkor keyboard was added. Able to see ស្រុក by typing key sequence s u j r k. Able to see that the reorder rule test, by hitting Backspace key. - ✅ **TEST_BASELINE_ADD_SPANISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598608540))**: Verified that the Spanish keyboard was added to the list. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598608540)) - ✅ **TEST_BASELINE_SWEDISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598608540))**: Verified that the given key sequences shows the expected output. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598608540)) - ✅ **TEST_SELECTION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: Tested in unminified Keymanweb test page and tested in both INPUT and TEXTAREA elements and here is my observations: 1. Verified that the output shows aqx. - ✅ **TEST_SELECTION_2 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: Verified that the output after the final key shows aqx. - ✅ **TEST_CONTEXT_BASE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: Verified that the output finally shows !. - ✅ **TEST_CONTEXT_SELECTION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: Verified that the output shows abcd. - ✅ **TEST_CONTEXT_SELECTION_2 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: Verified that the final key shows !. - ✅ **TEST_CONTEXT_SELECTION_3 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: Verified that the final key shows !. - ✅ **TEST_CONTEXT_SELECTION_4 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: Verified that the final key shows xdx. - ✅ **TEST_SELECTION_SHIFT ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: Verified that the pressing shift shows abcx with bc still selected. - ✅ **TEST_TYPING_AUTOSCROLL ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602185878))**: Retested as per Josh's suggestion and here my observation: 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field. - ✅ **TEST_ATTACHMENT_API ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly. - ✅ **TEST_NORMAL_USE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up. - ✅ **TEST_ELEMENT_HOPPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area. - ✅ **TEST_SPECIFIC_KEYBOARDS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine. - ✅ **TEST_JAPANESE_TYPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: 1. Able to add japanese keyboard. 2. Able to select the second option to replace the existing context. - ✅ **TEST_JAPANESE_FOCUS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600711550))**: 1. Verified that it is possible to see the japanese keyboard when I clicked either in text area or the input field. 2. If I clicked in the black area on the page, the keyboard disappeared. Seems to be working fine.

* ✅ GROUP_MACOS_SAFARI:

20 tests PASSED

- ✅ **TEST_BASELINE_ADD_SIL_IPA ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598753548))**: Verified that the key sequence n> produced ŋ. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598753548)) - ✅ **TEST_BASELINE_ADD_KM ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598753548))**: Verified that the Khmer_Basic keyboard was added. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598753548)) - ✅ **TEST_BASELINE_ADD_KHMER_ANGKOR ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598753548))**: Verified that the Khmer_angkor keyboard was added. Able to see ស្រុក by typing key sequence s u j r k. Able to see that the reorder rule test, by hitting Backspace key. - ✅ **TEST_BASELINE_ADD_SPANISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598753548))**: Verified that the Spanish keyboard was added to the list. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598753548)) - ✅ **TEST_BASELINE_SWEDISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598753548))**: Verified that the given key sequences shows the expected output. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598753548)) - ✅ **TEST_SELECTION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: Tested in unminified Keymanweb test page and tested in both INPUT and TEXTAREA elements and here is my observations: 1. Verified that the output shows aqx. - ✅ **TEST_SELECTION_2 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: Verified thta the output after the final key shows aqx. - ✅ **TEST_CONTEXT_BASE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: Verified that the output finally shows !. - ✅ **TEST_CONTEXT_SELECTION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: Verified that the output shows abcd. - ✅ **TEST_CONTEXT_SELECTION_2 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: Verified that the final key shows !. - ✅ **TEST_CONTEXT_SELECTION_3 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: Verified that the final key shows !. - ✅ **TEST_CONTEXT_SELECTION_4 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: Verified that the final key shows xdx. - ✅ **TEST_SELECTION_SHIFT ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: Verified that the pressing shift shows abcx with bc still selected. - ✅ **TEST_TYPING_AUTOSCROLL ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602185878))**: Retested as per Josh's suggestion and here my observation: 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field. - ✅ **TEST_ATTACHMENT_API ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly. - ✅ **TEST_NORMAL_USE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up. - ✅ **TEST_ELEMENT_HOPPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area. - ✅ **TEST_SPECIFIC_KEYBOARDS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine. - ✅ **TEST_JAPANESE_TYPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: 1. Able to add japanese keyboard. 2. Able to select the second option to replace the existing context. - ✅ **TEST_JAPANESE_FOCUS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1600949090))**: 1. Verified that it is possible to see the japanese keyboard when I clicked either in text area or the input field. 2. If I clicked in the black area on the page, the keyboard disappeared. Seems to be working fine.

* ✅ GROUP_MACOS_CHROME:

20 tests PASSED

- ✅ **TEST_BASELINE_ADD_SIL_IPA ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612))**: Verified that the key sequence n> produced ŋ. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612)) - ✅ **TEST_BASELINE_ADD_KM ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612))**: Verified that the Khmer_Basic keyboard was added. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612)) - ✅ **TEST_BASELINE_ADD_KHMER_ANGKOR ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612))**: Verified that the Khmer_angkor keyboard was added. Able to see ស្រុក by typing key sequence s u j r k. Able to see that the reorder rule test, by hitting Backspace key. - ✅ **TEST_BASELINE_ADD_SPANISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612))**: Verified that the Spanish keyboard was added to the list. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612)) - ✅ **TEST_BASELINE_SWEDISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612))**: Verified that the given key sequences shows the expected output. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612)) - ✅ **TEST_SELECTION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: Tested in unminified Keymanweb test page and tested in both INPUT and TEXTAREA elements and here is my observations: 1. Verified that the output shows aqx. - ✅ **TEST_SELECTION_2 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: Verified that the output after the final key shows aqx. - ✅ **TEST_CONTEXT_BASE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: Verified that the output finally shows !. - ✅ **TEST_CONTEXT_SELECTION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: Verified that the output shows abcd. - ✅ **TEST_CONTEXT_SELECTION_2 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: Verified that the final key shows !. - ✅ **TEST_CONTEXT_SELECTION_3 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: Verified that the final key shows !. - ✅ **TEST_CONTEXT_SELECTION_4 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: Verified that the final key shows xdx. - ✅ **TEST_SELECTION_SHIFT ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: Verified that the pressing shift shows abcx with bc still selected. - ✅ **TEST_TYPING_AUTOSCROLL ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field. - ✅ **TEST_ATTACHMENT_API ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly. - ✅ **TEST_NORMAL_USE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up. - ✅ **TEST_ELEMENT_HOPPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area. - ✅ **TEST_SPECIFIC_KEYBOARDS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine. - ✅ **TEST_JAPANESE_TYPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: 1. Able to add japanese keyboard. 2. Able to select the second option to replace the existing context. - ✅ **TEST_JAPANESE_FOCUS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602322212))**: 1. Verified that it is possible to see the japanese keyboard when I clicked either in text area or the input field. 2. If I clicked in the black area on the page, the keyboard disappeared. Seems to be working fine.

* ✅ GROUP_MACOS_FIREFOX:

20 tests PASSED

- ✅ **TEST_BASELINE_ADD_SIL_IPA ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612))**: Verified that the key sequence n> produced ŋ. - ✅ **TEST_BASELINE_ADD_KM ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612))**: Verified that the Khmer_Basic keyboard was added. - ✅ **TEST_BASELINE_ADD_KHMER_ANGKOR ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612))**: Verified that the Khmer_angkor keyboard was added. Able to see ស្រុក by typing key sequence s u j r k. Able to see that the reorder rule test, by hitting Backspace key. - ✅ **TEST_BASELINE_ADD_SPANISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612))**: Verified that the Spanish keyboard was added to the list. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612)) - ✅ **TEST_BASELINE_SWEDISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612))**: Verified that the given key sequences shows the expected output. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598840612)) - ✅ **TEST_SELECTION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: Tested in unminified Keymanweb test page and tested in both INPUT and TEXTAREA elements and here is my observations: 1. Verified that the output shows aqx. - ✅ **TEST_SELECTION_2 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: Verified that the output after the final key shows aqx. - ✅ **TEST_CONTEXT_BASE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: Verified that the output finally shows !. - ✅ **TEST_CONTEXT_SELECTION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: Verified that the output shows abcd. - ✅ **TEST_CONTEXT_SELECTION_2 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: Verified that the final key shows !. - ✅ **TEST_CONTEXT_SELECTION_3 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: Verified that the final key shows !. - ✅ **TEST_CONTEXT_SELECTION_4 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: Verified that the final key shows xdx. - ✅ **TEST_SELECTION_SHIFT ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: Verified that the pressing shift shows abcx with bc still selected. - ✅ **TEST_TYPING_AUTOSCROLL ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field. - ✅ **TEST_ATTACHMENT_API ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly. - ✅ **TEST_NORMAL_USE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up. - ✅ **TEST_ELEMENT_HOPPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area. - ✅ **TEST_SPECIFIC_KEYBOARDS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine. - ✅ **TEST_JAPANESE_TYPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: 1. Able to add japanese keyboard. 2. Able to select the second option to replace the existing context. - ✅ **TEST_JAPANESE_FOCUS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602473078))**: 1. Verified that it is possible to see the japanese keyboard when I clicked either in text area or the input field. 2. If I clicked in the black area on the page, the keyboard disappeared. Seems to be working fine.

* ✅ GROUP_LINUX_FIREFOX:

20 tests PASSED

- ✅ **TEST_BASELINE_ADD_SIL_IPA ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598640501))**: Verified that the key sequence n> produced ŋ. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598640501)) - ✅ **TEST_BASELINE_ADD_KM ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598640501))**: Verified that the Khmer_Basic keyboard was added. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598640501)) - ✅ **TEST_BASELINE_ADD_KHMER_ANGKOR ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598640501))**: Verified that the Khmer_angkor keyboard was added. Able to see ស្រុក by typing key sequence s u j r k. Able to see that the reorder rule test, by hitting Backspace key. - ✅ **TEST_BASELINE_ADD_SPANISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598640501))**: Verified that the Spanish keyboard was added to the list. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598640501)) - ✅ **TEST_BASELINE_SWEDISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598640501))**: Verified that the given key sequences shows the expected output. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1598640501)) - ✅ **TEST_SELECTION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: Tested in unminified Keymanweb test page and tested in both INPUT and TEXTAREA elements and here is my observations: 1. Verified that the output shows aqx. - ✅ **TEST_SELECTION_2 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: Verified that the output after the final key shows aqx. - ✅ **TEST_CONTEXT_BASE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: Verified that the output finally shows !. - ✅ **TEST_CONTEXT_SELECTION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: Verified that the output shows abcd. - ✅ **TEST_CONTEXT_SELECTION_2 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: Verified that the final key shows !. - ✅ **TEST_CONTEXT_SELECTION_3 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: Verified that the final key shows !. - ✅ **TEST_CONTEXT_SELECTION_4 ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: Verified that the final key shows xdx. - ✅ **TEST_SELECTION_SHIFT ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: Verified that the pressing shift shows abcx with bc still selected. - ✅ **TEST_TYPING_AUTOSCROLL ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field. - ✅ **TEST_ATTACHMENT_API ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly. - ✅ **TEST_NORMAL_USE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up. - ✅ **TEST_ELEMENT_HOPPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area. - ✅ **TEST_SPECIFIC_KEYBOARDS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine. - ✅ **TEST_JAPANESE_TYPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: 1. Able to add japanese keyboard. 2. Able to select the second option to replace the existing context. - ✅ **TEST_JAPANESE_FOCUS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602168025))**: 1. Verified that it is possible to see the japanese keyboard when I clicked either in text area or the input field. 2. If I clicked in the black area on the page, the keyboard disappeared. Seems to be working fine.

🟥 SUITE_TOUCH: Touch platform tests

✅ GROUP_ANDROID_CHROME_TOUCH:

12 tests PASSED
- ✅ **TEST_BASELINE_ADD_SIL_IPA ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425))**: Verified that pressing the subkey of n - shows the expected output. - ✅ **TEST_BASELINE_ADD_KM ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425))**: Verified that able to see the Khmer_basic keyboard. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425)) - ✅ **TEST_BASELINE_ADD_KHMER_ANGKOR ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425))**: Verified that typing the given sequence of letters on touch produces the expected output. Also, verified that pressing the Backspace key, delete the character one by one as per the reorder rule. - ✅ **TEST_BASELINE_ADD_SPANISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425))**: Verified that a Spanish keyboard is added to the list. - ✅ **TEST_BASELINE_SWEDISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425))**: 1. Verified that the two characters does not combine. 2. Verified that long pressing p or long pressing G displays the subkey menu and clicking on that produces expected output. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425)) - ✅ **TEST_BASELINE_CAMEROON ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425))**: 1. Verified that the top two rows of the symbol layer working correctly. 2. Verified that the tri-color key changes layer appropriately and that keys pressed automatically transition back to the default layer. 3. Verified that the subkey on the 'default' and on the 'shift' layers output the expected character. - ✅ **TEST_BASELINE_AUTOSCROLL ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425))**: 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field. - ✅ **TEST_ROTATION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425))**: 1. Verified that the OSK repositions itself at the bottom of the screen and occupies the full width of the device. (in both the roations - horizontal and vertical mode) - ✅ **TEST_ATTACHMENT_API ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425))**: 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly. - ✅ **TEST_NORMAL_USE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425))**: Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up. - ✅ **TEST_ELEMENT_HOPPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425))**: Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area. - ✅ **TEST_SPECIFIC_KEYBOARDS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425))**: Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602635425))
✅ GROUP_ANDROID_CHROME_HARDWARE:

12 tests PASSED
- ✅ **TEST_BASELINE_ADD_SIL_IPA ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602675838))**: Verified that pressing the subkey of n - shows the expected output. - ✅ **TEST_BASELINE_ADD_KM ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602675838))**: Verified that able to see the Khmer_basic keyboard. - ✅ **TEST_BASELINE_ADD_KHMER_ANGKOR ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602675838))**: Verified that typing the given sequence of letters on touch produces the expected output. Also, verified that pressing the Backspace key, delete the character one by one as per the reorder rule. - ✅ **TEST_BASELINE_ADD_SPANISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602675838))**: Verified that a Spanish keyboard is added to the list. - ✅ **TEST_BASELINE_SWEDISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602675838))**: 1. Verified that the two characters does not combine. 2. Verified that long pressing p or long pressing G displays the subkey menu and clicking on that produces expected output. - ✅ **TEST_BASELINE_CAMEROON ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602675838))**: 1. Verified that the top two rows of the symbol layer working correctly. 2. Verified that the tri-color key changes layer appropriately and that keys pressed automatically transition back to the default layer. 3. Verified that the subkey on the 'default' and on the 'shift' layers output the expected character. - ✅ **TEST_BASELINE_AUTOSCROLL ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602675838))**: 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field. - ✅ **TEST_ROTATION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602675838))**: 1. Verified that the OSK repositions itself at the bottom of the screen and occupies the full width of the device. (in both the rotations - horizontal and vertical mode) - ✅ **TEST_ATTACHMENT_API ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602675838))**: 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly. - ✅ **TEST_NORMAL_USE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602675838))**: Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up. - ✅ **TEST_ELEMENT_HOPPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602675838))**: Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area. - ✅ **TEST_SPECIFIC_KEYBOARDS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602675838))**: Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.
✅ GROUP_IPHONE_SAFARI_TOUCH:

12 tests PASSED
- ✅ **TEST_BASELINE_ADD_SIL_IPA ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476))**: Verified that pressing the subkey of n - shows the expected output. - ✅ **TEST_BASELINE_ADD_KM ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476))**: Verified that able to see the Khmer_basic keyboard. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476)) - ✅ **TEST_BASELINE_ADD_KHMER_ANGKOR ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476))**: Verified that typing the given sequence of letters on touch produces the expected output. Also, verified that pressing the Backspace key, delete the character one by one as per the reorder rule. - ✅ **TEST_BASELINE_ADD_SPANISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476))**: Verified that a Spanish keyboard is added to the list. - ✅ **TEST_BASELINE_SWEDISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476))**: 1. Verified that the two characters does not combine. 2. Verified that long pressing p or long pressing G displays the subkey menu and clicking on that produces expected output. - ✅ **TEST_BASELINE_CAMEROON ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476))**: 1. Verified that the top two rows of the symbol layer working correctly. 2. Verified that the tri-color key changes layer appropriately and that keys pressed automatically transition back to the default layer. 3. Verified that the subkey on the 'default' and on the 'shift' layers output the expected character. - ✅ **TEST_BASELINE_AUTOSCROLL ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476))**: 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476)) - ✅ **TEST_ROTATION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476))**: 1. Verified that the OSK repositions itself at the bottom of the screen and occupies the full width of the device. (in both the rotations - horizontal and vertical mode) - ✅ **TEST_ATTACHMENT_API ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476))**: 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly. - ✅ **TEST_NORMAL_USE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476))**: Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up. - ✅ **TEST_ELEMENT_HOPPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476))**: Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area. - ✅ **TEST_SPECIFIC_KEYBOARDS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476))**: Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine. ([notes](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602725476))
✅ GROUP_IPHONE_SAFARI_HARDWARE:

12 tests PASSED
- ✅ **TEST_BASELINE_ADD_SIL_IPA ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602735302))**: Verified that pressing the subkey of n - shows the expected output. - ✅ **TEST_BASELINE_ADD_KM ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602735302))**: Verified that able to see the Khmer_basic keyboard. - ✅ **TEST_BASELINE_ADD_KHMER_ANGKOR ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602735302))**: Verified that typing the given sequence of letters on touch produces the expected output. Also, verified that pressing the Backspace key, delete the character one by one as per the reorder rule. - ✅ **TEST_BASELINE_ADD_SPANISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602735302))**: Verified that a Spanish keyboard is added to the list. - ✅ **TEST_BASELINE_SWEDISH ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602735302))**: 1. Verified that the two characters does not combine. 2. Verified that long pressing p or long pressing G displays the subkey menu and clicking on that produces expected output. - ✅ **TEST_BASELINE_CAMEROON ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602735302))**: 1. Verified that the top two rows of the symbol layer working correctly. 2. Verified that the tri-color key changes layer appropriately and that keys pressed automatically transition back to the default layer. 3. Verified that the subkey on the 'default' and on the 'shift' layers output the expected character. - ✅ **TEST_BASELINE_AUTOSCROLL ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602735302))**: 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field. - ✅ **TEST_ROTATION ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602735302))**: 1. Verified that the OSK repositions itself at the bottom of the screen and occupies the full width of the device. (in both the rotations - horizontal and vertical mode) - ✅ **TEST_ATTACHMENT_API ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602735302))**: 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly. - ✅ **TEST_NORMAL_USE ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602735302))**: Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up. - ✅ **TEST_ELEMENT_HOPPING ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602735302))**: Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area. - ✅ **TEST_SPECIFIC_KEYBOARDS ([PASSED](https://github.com/keymanapp/keyman/issues/9037#issuecomment-1602735302))**: Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.
🟥 GROUP_IPAD_SAFARI_TOUCH:
- ✅ TEST_BASELINE_ADD_SIL_IPA (PASSED): Tested in iOS 16.4 / iPad (10th generation) Simulator and here is my observation: Verified that pressing the subkey of n - shows the expected output.
- ✅ TEST_BASELINE_ADD_KM (PASSED): Verified that able to see the Khmer_basic keyboard.
- 🟥 TEST_BASELINE_ADD_KHMER_ANGKOR (FAILED): Khmer Angkor keyboard does not show up the subkey. (notes)
- ✅ TEST_BASELINE_ADD_SPANISH (PASSED): Verified that a Spanish keyboard is added to the list. (notes)
- ✅ TEST_BASELINE_SWEDISH (PASSED): 1. Verified that the two characters does not combine. 2. Verified that long pressing p or long pressing G displays the subkey menu and clicking on that produces expected output. (notes)
- ✅ TEST_BASELINE_CAMEROON (PASSED): 1. Verified that the top two rows of the symbol layer working correctly. 2. Verified that the tri-color key changes layer appropriately and that keys pressed automatically transition back to the default layer. 3. Verified that the subkey on the 'default' and on the 'shift' layers output the expected character.
- ✅ TEST_BASELINE_AUTOSCROLL (PASSED): 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field. (notes)
- ✅ TEST_ROTATION (PASSED): 1. Verified that the OSK repositions itself at the bottom of the screen and occupies the full width of the device. (in both the roations - horizontal and vertical mode) (notes)
- ✅ TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
- ✅ TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
- ✅ TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
- ✅ TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine. (notes)
🟥 GROUP_IPAD_SAFARI_HARDWARE:
- ✅ TEST_BASELINE_ADD_SIL_IPA (PASSED): Verified that pressing the subkey of n - shows the expected output.
- ✅ TEST_BASELINE_ADD_KM (PASSED): Verified that able to see the Khmer_basic keyboard.
- 🟥 TEST_BASELINE_ADD_KHMER_ANGKOR (FAILED): Khmer Angkor keyboard does not show up the subkey.
- ✅ TEST_BASELINE_ADD_SPANISH (PASSED): Verified that a Spanish keyboard is added to the list.
- ✅ TEST_BASELINE_SWEDISH (PASSED): 1. Verified that the two characters does not combine. 2. Verified that long pressing p or long pressing G displays the subkey menu and clicking on that produces expected output.
- ✅ TEST_BASELINE_CAMEROON (PASSED): 1. Verified that the top two rows of the symbol layer working correctly. 2. Verified that the tri-color key changes layer appropriately and that keys pressed automatically transition back to the default layer. 3. Verified that the subkey on the 'default' and on the 'shift' layers output the expected character.
- ✅ TEST_BASELINE_AUTOSCROLL (PASSED): 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field.
- ✅ TEST_ROTATION (PASSED): 1. Verified that the OSK repositions itself at the bottom of the screen and occupies the full width of the device. (in both the roations - horizontal and vertical mode)
- ✅ TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
- ✅ TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
- ✅ TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
- ✅ TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.

Retesting Template

``` @keymanapp-test-bot retest SUITE_TOUCH GROUP_IPAD_SAFARI_TOUCH TEST_BASELINE_ADD_KHMER_ANGKOR GROUP_IPAD_SAFARI_HARDWARE TEST_BASELINE_ADD_KHMER_ANGKOR ```

SUITE_DESKTOP: Desktop Platforms

GROUP_WINDOWS_FIREFOX:

TEST_BASELINE_ADD_SIL_IPA (PASSED): Verified that the key sequence n> produced ŋ.
TEST_BASELINE_ADD_KM (PASSED): Verified that the Khmer_Basic keyboard was added.
TEST_BASELINE_ADD_KHMER_ANGKOR (PASSED): Verified that the Khmer_angkor keyboard was added. Able to see ស្រុក by typing key sequence s u j r k. Able to see that the reorder rule test, by hitting Backspace key.
TEST_BASELINE_ADD_SPANISH (PASSED): Verified that the Spanish keyboard was added to the list.
TEST_BASELINE_SWEDISH (PASSED): Verified that the given key sequences shows the expected output.

SUITE_DESKTOP: Desktop Platforms

GROUP_WINDOWS_CHROME:

TEST_BASELINE_ADD_SIL_IPA (PASSED): Verified that the key sequence n> produced ŋ.
TEST_BASELINE_ADD_KM (PASSED): Verified that the Khmer_Basic keyboard was added.
TEST_BASELINE_ADD_KHMER_ANGKOR (PASSED): Verified that the Khmer_angkor keyboard was added. Able to see ស្រុក by typing key sequence s u j r k. Able to see that the reorder rule test, by hitting Backspace key.
TEST_BASELINE_ADD_SPANISH (PASSED): Verified that the Spanish keyboard was added to the list.
TEST_BASELINE_SWEDISH (PASSED): Verified that the given key sequences shows the expected output.

SUITE_DESKTOP: Desktop Platforms

GROUP_LINUX_FIREFOX:

TEST_BASELINE_ADD_SIL_IPA (PASSED): Verified that the key sequence n> produced ŋ.
TEST_BASELINE_ADD_KM (PASSED): Verified that the Khmer_Basic keyboard was added.
TEST_BASELINE_ADD_KHMER_ANGKOR (PASSED): Verified that the Khmer_angkor keyboard was added. Able to see ស្រុក by typing key sequence s u j r k. Able to see that the reorder rule test, by hitting Backspace key.
TEST_BASELINE_ADD_SPANISH (PASSED): Verified that the Spanish keyboard was added to the list.
TEST_BASELINE_SWEDISH (PASSED): Verified that the given key sequences shows the expected output.

SUITE_DESKTOP: Desktop Platforms

GROUP_MACOS_SAFARI:

TEST_BASELINE_ADD_SIL_IPA (PASSED): Verified that the key sequence n> produced ŋ.
TEST_BASELINE_ADD_KM (PASSED): Verified that the Khmer_Basic keyboard was added.
TEST_BASELINE_ADD_KHMER_ANGKOR (PASSED): Verified that the Khmer_angkor keyboard was added. Able to see ស្រុក by typing key sequence s u j r k. Able to see that the reorder rule test, by hitting Backspace key.
TEST_BASELINE_ADD_SPANISH (PASSED): Verified that the Spanish keyboard was added to the list.
TEST_BASELINE_SWEDISH (PASSED): Verified that the given key sequences shows the expected output.

SUITE_DESKTOP: Desktop Platforms

GROUP_MACOS_CHROME:

TEST_BASELINE_ADD_SIL_IPA (PASSED): Verified that the key sequence n> produced ŋ.
TEST_BASELINE_ADD_KM (PASSED): Verified that the Khmer_Basic keyboard was added.
TEST_BASELINE_ADD_KHMER_ANGKOR (PASSED): Verified that the Khmer_angkor keyboard was added. Able to see ស្រុក by typing key sequence s u j r k. Able to see that the reorder rule test, by hitting Backspace key.
TEST_BASELINE_ADD_SPANISH (PASSED): Verified that the Spanish keyboard was added to the list.
TEST_BASELINE_SWEDISH (PASSED): Verified that the given key sequences shows the expected output.

GROUP_MACOS_FIREFOX:

TEST_BASELINE_ADD_SIL_IPA (PASSED): Verified that the key sequence n> produced ŋ.
TEST_BASELINE_ADD_KM (PASSED): Verified that the Khmer_Basic keyboard was added.
TEST_BASELINE_ADD_KHMER_ANGKOR (PASSED): Verified that the Khmer_angkor keyboard was added. Able to see ស្រុក by typing key sequence s u j r k. Able to see that the reorder rule test, by hitting Backspace key.
TEST_BASELINE_ADD_SPANISH (PASSED): Verified that the Spanish keyboard was added to the list.
TEST_BASELINE_SWEDISH (PASSED): Verified that the given key sequences shows the expected output.

SUITE_DESKTOP: Desktop Platforms

GROUP_WINDOWS_FIREFOX:

TEST_SELECTION (PASSED): Tested in unminified Keymanweb test page and tested in both INPUT and TEXTAREA elements and here is my observations: 1. Verified that the output shows aqx.
TEST_SELECTION_2 (PASSED): Verified that the output after the final key shows aqx.
TEST_CONTEXT_BASE (PASSED): Verified that the output finally shows !.
TEST_CONTEXT_SELECTION (PASSED): Verified that the output shows abcd.
TEST_CONTEXT_SELECTION_2 (PASSED): Verified that the final key shows !.
TEST_CONTEXT_SELECTION_3 (PASSED): Verified that the final key shows !.
TEST_CONTEXT_SELECTION_4 (PASSED): Verified that the final key shows xdx.
TEST_SELECTION_SHIFT (PASSED): Verified that the pressing shift shows abcx with bc still selected.

Shift_firefox

TEST_TYPING_AUTOSCROLL (FAILED): Verified that the text autoscroll is not working in INPUT field.

..inputfield

SUITE_DESKTOP: Desktop Platforms

GROUP_WINDOWS_FIREFOX:

TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.
TEST_JAPANESE_TYPING (PASSED): 1. Able to add japanese keyboard. 2. Able to select the second option to replace the existing context.
TEST_JAPANESE_FOCUS (PASSED): 1. Verified that it is possible to see the japanese keyboard when I clicked either in text area or the input field. 2. If I clicked in the black area on the page, the keyboard disappeared. Seems to be working fine.

SUITE_DESKTOP: Desktop Platforms

GROUP_WINDOWS_CHROME:

TEST_SELECTION (PASSED): Tested in unminified Keymanweb test page and tested in both INPUT and TEXTAREA elements and here is my observations: 1. Verified that the output shows aqx.
TEST_SELECTION_2 (PASSED): Verified that the output after the final key shows aqx.
TEST_CONTEXT_BASE (PASSED): Verified that the output finally shows !.
TEST_CONTEXT_SELECTION (PASSED): Verified that the output shows abcd.
TEST_CONTEXT_SELECTION_2 (PASSED): Verified that the final key shows !.
TEST_CONTEXT_SELECTION_3 (PASSED): Verified that the final key shows !.
TEST_CONTEXT_SELECTION_4 (PASSED): Verified that the final key shows xdx.
TEST_SELECTION_SHIFT (PASSED): Verified that the pressing shift shows abcx with bc still selected.
TEST_TYPING_AUTOSCROLL (FAILED): Noticed that the autoscroll does not happen in the INPUT field. Seems to be an issue.
TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.
TEST_JAPANESE_TYPING (PASSED): 1. Able to add japanese keyboard. 2. Able to select the second option to replace the existing context.
TEST_JAPANESE_FOCUS (PASSED): 1. Verified that it is possible to see the japanese keyboard when I clicked either in text area or the input field. 2. If I clicked in the black area on the page, the keyboard disappeared. Seems to be working fine.

SUITE_DESKTOP: Desktop Platforms

GROUP_MACOS_SAFARI:

TEST_SELECTION (PASSED): Tested in unminified Keymanweb test page and tested in both INPUT and TEXTAREA elements and here is my observations: 1. Verified that the output shows aqx.
TEST_SELECTION_2 (PASSED): Verified thta the output after the final key shows aqx.
TEST_CONTEXT_BASE (PASSED): Verified that the output finally shows !.
TEST_CONTEXT_SELECTION (PASSED): Verified that the output shows abcd.
TEST_CONTEXT_SELECTION_2 (PASSED): Verified that the final key shows !.
TEST_CONTEXT_SELECTION_3 (PASSED): Verified that the final key shows !.
TEST_CONTEXT_SELECTION_4 (PASSED): Verified that the final key shows xdx.
TEST_SELECTION_SHIFT (PASSED): Verified that the pressing shift shows abcx with bc still selected.
TEST_TYPING_AUTOSCROLL (FAILED): Noticed that AutoScroll is not working in INPUT field.
TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.
TEST_JAPANESE_TYPING (PASSED): 1. Able to add japanese keyboard. 2. Able to select the second option to replace the existing context.
TEST_JAPANESE_FOCUS (PASSED): 1. Verified that it is possible to see the japanese keyboard when I clicked either in text area or the input field. 2. If I clicked in the black area on the page, the keyboard disappeared. Seems to be working fine.

@bharanidharanj

TEST_TYPING_AUTOSCROLL (FAILED): Verified that the text autoscroll is not working in INPUT field.

..inputfield

... but it did autoscroll. Note the left-hand side of the input field. I'm assuming that you just typed the word testing over and over again... so why is the first thing visible in the input field ting, not testing? It's because the first copy's tes got "autoscrolled" off the left-hand side.

Note how you can still see the caret at the end of the input field, too:

From the test's definition:

Verify that the text is automatically scrolled so that the last three characters and the caret (the thin, blinking | mark for text position) are visible.

Your ing is visible, as well as the caret. It totally PASSES.

@bharanidharanj

TEST_TYPING_AUTOSCROLL (FAILED): Verified that the text autoscroll is not working in INPUT field.

..inputfield

... but it did autoscroll. Note the left-hand side of the input field. I'm assuming that you just typed the word testing over and over again... so why is the first thing visible in the input field ting, not testing? It's because the first copy's tes got "autoscrolled" off the left-hand side.

Note how you can still see the caret at the end of the input field, too:

From the test's definition:

Verify that the text is automatically scrolled so that the last three characters and the caret (the thin, blinking | mark for text position) are visible.

Your ing is visible, as well as the caret. It totally PASSES.

@jahorton I thought after typing the last 3 characters the word 'testing' will jump into the next line (ie., move down to next line ..like in text area). Now, I can understand the procedure. Thanks for the Clarification. :-)

@keymanapp-test-bot retest SUITE_DESKTOP TEST_TYPING_AUTOSCROLL (To reset the test that just got clarified)

SUITE_DESKTOP: Desktop Platforms

GROUP_LINUX_FIREFOX:

TEST_SELECTION (PASSED): Tested in unminified Keymanweb test page and tested in both INPUT and TEXTAREA elements and here is my observations: 1. Verified that the output shows aqx.
TEST_SELECTION_2 (PASSED): Verified that the output after the final key shows aqx.
TEST_CONTEXT_BASE (PASSED): Verified that the output finally shows !.
TEST_CONTEXT_SELECTION (PASSED): Verified that the output shows abcd.
TEST_CONTEXT_SELECTION_2 (PASSED): Verified that the final key shows !.
TEST_CONTEXT_SELECTION_3 (PASSED): Verified that the final key shows !.
TEST_CONTEXT_SELECTION_4 (PASSED): Verified that the final key shows xdx.
TEST_SELECTION_SHIFT (PASSED): Verified that the pressing shift shows abcx with bc still selected.
TEST_TYPING_AUTOSCROLL (PASSED): 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field.
TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.
TEST_JAPANESE_TYPING (PASSED): 1. Able to add japanese keyboard. 2. Able to select the second option to replace the existing context.
TEST_JAPANESE_FOCUS (PASSED): 1. Verified that it is possible to see the japanese keyboard when I clicked either in text area or the input field. 2. If I clicked in the black area on the page, the keyboard disappeared. Seems to be working fine.

SUITE_DESKTOP: Desktop Platforms

GROUP_WINDOWS_FIREFOX:

TEST_TYPING_AUTOSCROLL (PASSED): Retested as per Josh's suggestion and here my observation: 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field.

GROUP_WINDOWS_CHROME:

TEST_TYPING_AUTOSCROLL (PASSED): Retested as per Josh's suggestion and here my observation: 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field.

GROUP_MACOS_SAFARI:

TEST_TYPING_AUTOSCROLL (PASSED): Retested as per Josh's suggestion and here my observation: 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field.

SUITE_DESKTOP: Desktop Platforms

GROUP_MACOS_CHROME:

TEST_SELECTION (PASSED): Tested in unminified Keymanweb test page and tested in both INPUT and TEXTAREA elements and here is my observations: 1. Verified that the output shows aqx.
TEST_SELECTION_2 (PASSED): Verified that the output after the final key shows aqx.
TEST_CONTEXT_BASE (PASSED): Verified that the output finally shows !.
TEST_CONTEXT_SELECTION (PASSED): Verified that the output shows abcd.
TEST_CONTEXT_SELECTION_2 (PASSED): Verified that the final key shows !.
TEST_CONTEXT_SELECTION_3 (PASSED): Verified that the final key shows !.
TEST_CONTEXT_SELECTION_4 (PASSED): Verified that the final key shows xdx.
TEST_SELECTION_SHIFT (PASSED): Verified that the pressing shift shows abcx with bc still selected.
TEST_TYPING_AUTOSCROLL (PASSED): 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field.
TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.
TEST_JAPANESE_TYPING (PASSED): 1. Able to add japanese keyboard. 2. Able to select the second option to replace the existing context.
TEST_JAPANESE_FOCUS (PASSED): 1. Verified that it is possible to see the japanese keyboard when I clicked either in text area or the input field. 2. If I clicked in the black area on the page, the keyboard disappeared. Seems to be working fine.

SUITE_DESKTOP: Desktop Platforms

GROUP_MACOS_FIREFOX:

TEST_SELECTION (PASSED): Tested in unminified Keymanweb test page and tested in both INPUT and TEXTAREA elements and here is my observations: 1. Verified that the output shows aqx.
TEST_SELECTION_2 (PASSED): Verified that the output after the final key shows aqx.
TEST_CONTEXT_BASE (PASSED): Verified that the output finally shows !.
TEST_CONTEXT_SELECTION (PASSED): Verified that the output shows abcd.
TEST_CONTEXT_SELECTION_2 (PASSED): Verified that the final key shows !.
TEST_CONTEXT_SELECTION_3 (PASSED): Verified that the final key shows !.
TEST_CONTEXT_SELECTION_4 (PASSED): Verified that the final key shows xdx.
TEST_SELECTION_SHIFT (PASSED): Verified that the pressing shift shows abcx with bc still selected.
TEST_TYPING_AUTOSCROLL (PASSED): 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field.
TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.
TEST_JAPANESE_TYPING (PASSED): 1. Able to add japanese keyboard. 2. Able to select the second option to replace the existing context.
TEST_JAPANESE_FOCUS (PASSED): 1. Verified that it is possible to see the japanese keyboard when I clicked either in text area or the input field. 2. If I clicked in the black area on the page, the keyboard disappeared. Seems to be working fine.

SUITE_TOUCH: Touch platform tests

GROUP_ANDROID_CHROME_TOUCH:

TEST_BASELINE_ADD_SIL_IPA (PASSED): Verified that pressing the subkey of n - shows the expected output.
TEST_BASELINE_ADD_KM PASSED): Verified that able to see the Khmer_basic keyboard.
TEST_BASELINE_ADD_KHMER_ANGKOR (PASSED): Verified that typing the given sequence of letters on touch produces the expected output. Also, verified that pressing the Backspace key, delete the character one by one as per the reorder rule.
TEST_BASELINE_ADD_SPANISH (PASSED): Verified that a Spanish keyboard is added to the list.
TEST_BASELINE_SWEDISH (PASSED): 1. Verified that the two characters does not combine. 2. Verified that long pressing p or long pressing G displays the subkey menu and clicking on that produces expected output.
TEST_BASELINE_CAMEROON (PASSED): 1. Verified that the top two rows of the symbol layer working correctly. 2. Verified that the tri-color key changes layer appropriately and that keys pressed automatically transition back to the default layer. 3. Verified that the subkey on the 'default' and on the 'shift' layers output the expected character.
TEST_BASELINE_AUTOSCROLL PASSED): 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field.
TEST_ROTATION (PASSED): 1. Verified that the OSK repositions itself at the bottom of the screen and occupies the full width of the device. (in both the roations - horizontal and vertical mode)
TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.

SUITE_TOUCH: Touch platform tests

GROUP_ANDROID_CHROME_HARDWARE:

TEST_BASELINE_ADD_SIL_IPA (PASSED): Verified that pressing the subkey of n - shows the expected output.
TEST_BASELINE_ADD_KM (PASSED): Verified that able to see the Khmer_basic keyboard.
TEST_BASELINE_ADD_KHMER_ANGKOR (PASSED): Verified that typing the given sequence of letters on touch produces the expected output. Also, verified that pressing the Backspace key, delete the character one by one as per the reorder rule.
TEST_BASELINE_ADD_SPANISH (PASSED): Verified that a Spanish keyboard is added to the list.
TEST_BASELINE_SWEDISH (PASSED): 1. Verified that the two characters does not combine. 2. Verified that long pressing p or long pressing G displays the subkey menu and clicking on that produces expected output.
TEST_BASELINE_CAMEROON (PASSED): 1. Verified that the top two rows of the symbol layer working correctly. 2. Verified that the tri-color key changes layer appropriately and that keys pressed automatically transition back to the default layer. 3. Verified that the subkey on the 'default' and on the 'shift' layers output the expected character.
TEST_BASELINE_AUTOSCROLL (PASSED): 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field.
TEST_ROTATION (PASSED): 1. Verified that the OSK repositions itself at the bottom of the screen and occupies the full width of the device. (in both the rotations - horizontal and vertical mode)
TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.

SUITE_TOUCH: Touch platform tests

GROUP_IPHONE_SAFARI_TOUCH:

TEST_BASELINE_ADD_SIL_IPA (PASSED): Verified that pressing the subkey of n - shows the expected output.
TEST_BASELINE_ADD_KM (PASSED): Verified that able to see the Khmer_basic keyboard.
TEST_BASELINE_ADD_KHMER_ANGKOR (PASSED): Verified that typing the given sequence of letters on touch produces the expected output. Also, verified that pressing the Backspace key, delete the character one by one as per the reorder rule.
TEST_BASELINE_ADD_SPANISH (PASSED): Verified that a Spanish keyboard is added to the list.
TEST_BASELINE_SWEDISH (PASSED): 1. Verified that the two characters does not combine. 2. Verified that long pressing p or long pressing G displays the subkey menu and clicking on that produces expected output.
TEST_BASELINE_CAMEROON (PASSED): 1. Verified that the top two rows of the symbol layer working correctly. 2. Verified that the tri-color key changes layer appropriately and that keys pressed automatically transition back to the default layer. 3. Verified that the subkey on the 'default' and on the 'shift' layers output the expected character.
TEST_BASELINE_AUTOSCROLL (PASSED): 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field.
TEST_ROTATION (PASSED): 1. Verified that the OSK repositions itself at the bottom of the screen and occupies the full width of the device. (in both the rotations - horizontal and vertical mode)
TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.

SUITE_TOUCH: Touch platform tests

GROUP_IPHONE_SAFARI_HARDWARE:

TEST_BASELINE_ADD_SIL_IPA (PASSED): Verified that pressing the subkey of n - shows the expected output.
TEST_BASELINE_ADD_KM (PASSED): Verified that able to see the Khmer_basic keyboard.
TEST_BASELINE_ADD_KHMER_ANGKOR (PASSED): Verified that typing the given sequence of letters on touch produces the expected output. Also, verified that pressing the Backspace key, delete the character one by one as per the reorder rule.
TEST_BASELINE_ADD_SPANISH (PASSED): Verified that a Spanish keyboard is added to the list.
TEST_BASELINE_SWEDISH (PASSED): 1. Verified that the two characters does not combine. 2. Verified that long pressing p or long pressing G displays the subkey menu and clicking on that produces expected output.
TEST_BASELINE_CAMEROON (PASSED): 1. Verified that the top two rows of the symbol layer working correctly. 2. Verified that the tri-color key changes layer appropriately and that keys pressed automatically transition back to the default layer. 3. Verified that the subkey on the 'default' and on the 'shift' layers output the expected character.
TEST_BASELINE_AUTOSCROLL (PASSED): 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field.
TEST_ROTATION (PASSED): 1. Verified that the OSK repositions itself at the bottom of the screen and occupies the full width of the device. (in both the rotations - horizontal and vertical mode)
TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.

SUITE_TOUCH: Touch platform tests

GROUP_IPAD_SAFARI_TOUCH:

TEST_BASELINE_ADD_SIL_IPA (PASSED): Tested in iOS 16.4 / iPad (10th generation) Simulator and here is my observation: Verified that pressing the subkey of n - shows the expected output.
TEST_BASELINE_ADD_KM (PASSED): Verified that able to see the Khmer_basic keyboard.
TEST_BASELINE_ADD_KHMER_ANGKOR (FAILED): Khmer Angkor keyboard does not show up the subkey.
TEST_BASELINE_ADD_SPANISH (PASSED): Verified that a Spanish keyboard is added to the list.
TEST_BASELINE_SWEDISH (PASSED): 1. Verified that the two characters does not combine. 2. Verified that long pressing p or long pressing G displays the subkey menu and clicking on that produces expected output.
TEST_BASELINE_CAMEROON (PASSED): 1. Verified that the top two rows of the symbol layer working correctly. 2. Verified that the tri-color key changes layer appropriately and that keys pressed automatically transition back to the default layer. 3. Verified that the subkey on the 'default' and on the 'shift' layers output the expected character.
TEST_BASELINE_AUTOSCROLL (PASSED): 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field.
TEST_ROTATION (PASSED): 1. Verified that the OSK repositions itself at the bottom of the screen and occupies the full width of the device. (in both the roations - horizontal and vertical mode) ..Portrait

..Landscape

TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.

GROUP_IPAD_SAFARI_HARDWARE:

TEST_BASELINE_ADD_SIL_IPA (PASSED): Verified that pressing the subkey of n - shows the expected output.
TEST_BASELINE_ADD_KM (PASSED): Verified that able to see the Khmer_basic keyboard.
TEST_BASELINE_ADD_KHMER_ANGKOR (FAILED): Khmer Angkor keyboard does not show up the subkey.
TEST_BASELINE_ADD_SPANISH (PASSED): Verified that a Spanish keyboard is added to the list.
TEST_BASELINE_SWEDISH (PASSED): 1. Verified that the two characters does not combine. 2. Verified that long pressing p or long pressing G displays the subkey menu and clicking on that produces expected output.
TEST_BASELINE_CAMEROON (PASSED): 1. Verified that the top two rows of the symbol layer working correctly. 2. Verified that the tri-color key changes layer appropriately and that keys pressed automatically transition back to the default layer. 3. Verified that the subkey on the 'default' and on the 'shift' layers output the expected character.
TEST_BASELINE_AUTOSCROLL (PASSED): 1. Verified that the text is automatically scrolled so that the last three characters and the caret are fully visible. 2. Verified that the Keyboard is still visible at any point while typing in the input field.
TEST_ROTATION (PASSED): 1. Verified that the OSK repositions itself at the bottom of the screen and occupies the full width of the device. (in both the roations - horizontal and vertical mode)
TEST_ATTACHMENT_API (PASSED): 1. Verified that the 'auto' attachment mode properly and automatically attached to each dynamically-added control. 2. Verified the 'manual' attachment mode results in a page with no KMW-activated controls. 3. Verified that each 'attached' control functions as expected for the selected keyboard(s). 4. Verified that the KeymanWeb properly attaches to and detaches from each relevant type of control. Also, verified that the independent-keyboard management API functions correctly.
TEST_NORMAL_USE (PASSED): Tested in the given test page and here is my observation : 1. Verified that the keyboard displays and works correctly when the first loaded up.
TEST_ELEMENT_HOPPING (PASSED): Verified that the OSK remains visible if I jump to another page element and it is automatically hidden if I clicked on the blank area.
TEST_SPECIFIC_KEYBOARDS (PASSED): Verified that the keyboard changes from one dynamic area to other and it is showing the expected keyboard layout. Seems to be working fine.

OK... so the two test failures are because the tablet form-factor layout for khmer_angkor doesn't use subkeys to the same extent as the phone form-factor layout. I've gone ahead and adjusted the description accordingly.

Looks like everything else passed swimmingly, so... I think that means we're good to go.

For updating the Platform Acceptance Test for Web wiki page:

Do include the wiki page's SUITE_INSPECT in its original position.
Replace all other SUITEs with their specs from the description of this PR.
Do a find-and-replace on all Web test-page links when copying the description text over: Keymanweb_TestPullRequests/390024:id/src => Keymanweb_TestPullRequests/TBD:id/src, since that's the pattern we've been using for the platform-acceptance user testing template.

8560 has merged! 🎊

As this was a testing issue for that branch, we can retire this issue now.

keymanapp / keyman

test(web): feature-branch regression testing - ES modules (🧩), main suite #9037

Keyman for Web Acceptance Test Procedures

User Testing

SUITE_DESKTOP: Desktop Platforms

Baseline Tests

Text Selection Tests

Element Attachment Tests

Site-based tests of attachment API

Tests CJK keyboard functionality

SUITE_TOUCH: Touch platform tests

Baseline Tests

Element Attachment Tests

Site-based tests of attachment API

User Test Results

✅ SUITE_DESKTOP: Desktop Platforms

🟥 SUITE_TOUCH: Touch platform tests

SUITE_DESKTOP: Desktop Platforms

GROUP_WINDOWS_FIREFOX:

SUITE_DESKTOP: Desktop Platforms

GROUP_WINDOWS_CHROME:

SUITE_DESKTOP: Desktop Platforms

GROUP_LINUX_FIREFOX:

SUITE_DESKTOP: Desktop Platforms

GROUP_MACOS_SAFARI:

SUITE_DESKTOP: Desktop Platforms

GROUP_MACOS_CHROME:

GROUP_MACOS_FIREFOX:

SUITE_DESKTOP: Desktop Platforms

GROUP_WINDOWS_FIREFOX:

SUITE_DESKTOP: Desktop Platforms

GROUP_WINDOWS_FIREFOX:

SUITE_DESKTOP: Desktop Platforms

GROUP_WINDOWS_CHROME:

SUITE_DESKTOP: Desktop Platforms

GROUP_MACOS_SAFARI:

SUITE_DESKTOP: Desktop Platforms

GROUP_LINUX_FIREFOX:

SUITE_DESKTOP: Desktop Platforms

GROUP_WINDOWS_FIREFOX:

GROUP_WINDOWS_CHROME:

GROUP_MACOS_SAFARI:

SUITE_DESKTOP: Desktop Platforms

GROUP_MACOS_CHROME:

SUITE_DESKTOP: Desktop Platforms

GROUP_MACOS_FIREFOX:

SUITE_TOUCH: Touch platform tests

GROUP_ANDROID_CHROME_TOUCH:

SUITE_TOUCH: Touch platform tests

GROUP_ANDROID_CHROME_HARDWARE:

SUITE_TOUCH: Touch platform tests

GROUP_IPHONE_SAFARI_TOUCH:

SUITE_TOUCH: Touch platform tests

GROUP_IPHONE_SAFARI_HARDWARE:

SUITE_TOUCH: Touch platform tests

GROUP_IPAD_SAFARI_TOUCH:

GROUP_IPAD_SAFARI_HARDWARE:

8560 has merged! 🎊