-
-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(web,developer): Move keymanweb-osk.ttf to common/resources #9993
Conversation
User Test ResultsTest specification and instructions
Test Artifacts
|
@@ -36,7 +36,12 @@ builder_parse "$@" | |||
|
|||
#### Build action definitions #### | |||
|
|||
builder_run_action configure verify_npm_setup | |||
if builder_start_action configure; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
builder_describe_outputs (line 32) needs configure
to point to the font, because /node_modules
is already present, so this step is skipped.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs user tests. I'm requesting changes on the basis of the test-bot skip
command. (There's a noticeable chance for breakage in how the font resource gets included in the build and/or linked for use on the test pages.)
TEST_WEB_OSK: Using the "Test unminified KeymanWeb" test page, verify that all OSK keys still show up properly.
- Load the page.
- Click in a text area so that the OSK becomes visible.
- Inspect all keys. If any has text beginning with and ending with
**
, FAIL this test.- Such keys would normally have special OSK symbols on them.
TEST_DEVELOPER_WEB_OSK: Using the Developer test-host page for testing Web keyboards, verify that all OSK keys still show up properly.
- Load a keyboard project. (Say,
release/sil/sil_euro_latin
from thekeymanapp/keyboards
repo. - Build the keyboard.
- Test the keyboard using Web, starting the test server and using one of Developer's links to start the test page.
- Click in a text area so that the OSK becomes visible.
- Inspect all keys. If any has text beginning with and ending with
**
, FAIL this test.- Such keys would normally have special OSK symbols on them.
A similar test for one of the mobile apps (Android, iOS) may also be wise. And feel free to change the directions for the two tests I did spec above to be clearer and/or more specific about the steps if needed.
@@ -30,13 +30,19 @@ builder_describe "Builds the Keyman Engine for Web's On-Screen Keyboard package | |||
|
|||
builder_describe_outputs \ | |||
configure /node_modules \ | |||
configure /web/src/resources/osk/keymanweb-osk.ttf \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait... can the builder-script setup actually support two separate lines for the same action:target
without losing one of them? If so... wish I'd known that; there's a lot of Web scripts that could use multiple output-checks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm hoping that syntax works. builder.inc failed when I originally had
configure /node_modules \
/web/src/resources/osk/keymanweb-osk.ttf \
build ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, currently it's only one output per target. Anything more is a future builder feature.
Requested user tests have now been spec'd.
Co-authored-by: Marc Durdin <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry to say that the Developer build scripts are still Makefile-based, so we'll have to refactor that 😭
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me
Changes in this pull request will be available for download in Keyman version 17.0.211-alpha |
Unfortunately sil_euro_latin doesn't use the standard OSK and none of the special characters would be visible, so this test result is invalid. |
Follow-on to #9846
Since Developer and Web use the same keymanweb-osk.ttf resource, this PR moves it to /common/resources/fonts
and updates the configure step accordingly.
(edit to add @jahorton tests)
User Testing
Such keys would normally have special OSK symbols on them.
Setup - Install the PR build of KeyboardHarness on an Android device/emulator (newer than Android 5.0)