Skip to content

Name build-481d83c as the build the keyboard and pointer fixes shipped in #94

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.

Sign up for GitHub

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

Merged
PatrickSt1991 merged 1 commit into from
Sep 9, 2026
Merged

Name build-481d83c as the build the keyboard and pointer fixes shipped in #94

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/INTERNALS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2801,8 +2801,8 @@ the one its report has to come from. The state is:
coming back on a `visibilitychange` after the app had hidden it to draw its
own; the hide is remembered now. See *The selector follows the screen, not the
index* and *The page's arrow has to remember it was told to go away* above.
Both fixes are in `src/common`, so the ewk builds get them too. **Waiting on:**
his report from the build. Neither needs a question answered — the keyboard
Both fixes are in `src/common`, so the ewk builds get them too. Shipped in
`build-481d83c`. **Waiting on:** his report from that build. Neither needs a question answered — the keyboard
either lands under the key or it does not, and either one pointer shows at
launch or two do. If two still do, the `pointer` line on the report says who is
drawing the one we mean, and the next thing to look for is a second
Expand Down