Step 5 can be done using left-arrow instead. Skip step 4 - mouse doesn't move insertion point in Terminal. Terminal (known compatibility issues: Steps 1 & 3 insert an extra leading space if there are no preceding characters.
b) New message in existing conversation, such that the message area has grayed out text: "iMessage").a) New message with nobody filled in in To: line.There seems to be a certain level of general twitchiness, with extra characters sometimes being displayed - sometimes only briefly - and characters being deleted.)įirefox browser Google Docs document (currently known compatibility issue for steps 3, 4 & 5 because any selection change will cause the context to be reset - Google docs can't report context.) Step 8 fails for the same reason it doesn't work at the beginning of the paragraph.
b) Elsewhere in paragraph (occasionally steps 4 & 5 deletes a preceding (space?) character, but I haven't figured out when/why.a) Beginning of paragraph (currently known compatibility issues steps 1, 3, 4 & 5, 7&8).Safari browser Google Docs document (currently known compatibility issue for steps 3, 4 & 5 because any selection change will cause the context to be reset - Google docs can't report context.) a) Beginning of paragraph (currently known compatibility issues steps 1, 3, 4 & 5)Ītom editor - test in Snippet editor (currently known compatibility issue for steps 3, 4 & 5).Typing at, then ⌘-A, followed by a produces አ.Ĭhrome browser Google Docs document (currently known compatibility issue for steps 3, 4 & 5 because any selection change will cause the context to be reset - Google docs can't report context.)Ĭhrome browser Word Online Note: Not using the Office Extension for Chrome - not sure if that would make a difference With a few characters displayed, ⌘-A followed by typing t replaces selected characters with ት. The "normal" behavior in all three browsers is to activate the Google Docs command, not the browser command, with the exception that ⌘-O in Safari opens Safari's standard macOS Open file dialog.) (Note that in Google Docs, these commands correspond to both a Google-Docs command and a browser command. For example: ⌘-F (typically opens a Find dialog or control) ⌘-O (File Open) ⌘-X (Cut) ⌘-C (Copy) ⌘-V (Paste) ⌘-A (Select All). In each of the last three cases, the insertion point should end up before the final ት character.Ĭommon keyboard shortcuts for the app work as expected. Typing tt, then mouse-clicking between the two ታ characters, and then typing a produces ታት. For each of the following applications/contexts, test that If you click No, the configuration window should not be displayed (but there is a known issue that the very first time after Keyman loads, if the configuration window has not been shown, it will be displayed even if the user clicks No). If you click Yes, the package should be installed (or updated) and the configuration window should display, showing that the keyboard(s) in the package are installed and enabled.
Typing master keyman install#
Should see a “Do you want the Keyman Input Method to install this Package?“ message. Should see several keyboards, including some by The Ge'ez Frontier Foundation and some by SIL.ĭouble-click any KMP file (in Finder). Verify that page displays correctly (should have a Keyboard Search box with the prompt: Enter language or keyboard. On device, re-enable Internet connectivityĪctivate Keyman and select Keyman Configuration from the input methods menu. Verify error message "Could not reach Keyman server!" is displayed (This is currently not happening. On device, turn Wifi off and/or disconnect Ethernet cableĪctivate Keyman and select Keyman Configuration from the input methods menu. Verify that the version displayed in the About box is correct. Install latest master build (or whatever version is to be tested) of Keyman on the device Uninstall previous version of Keyman on the device Verify mac/history.md contains all the current changesĮnsure the device is running the latest version of macOS Verify latest CI build of master is successful