Repository navigation
Version Packages - #233
Open
github-actions[bot] wants to merge 1 commit into
Open
Version Packages#233github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 16, 2026 17:57
b523baf to
b848041
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 17, 2026 05:43
b848041 to
3c021b6
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@typeonce/ritmo-browser@0.25.0
Minor Changes
cd6bb2e: Breaking (a fix to 0.24's modal rule):
Keyboard.actionsleaves every key to the page while a modal dialog is open, wherever focus is. In 0.24 a key was the page's only when its target was inside the modal. When a redraw deleted the focused button inside an open<dialog>, focus fell to<body>and the game took the keys again: Z and Space pressed game actions behind the menu, and Escape pressed the game's action and waspreventDefault-ed, so the dialog did not close.A modal is now open when the key's document holds a
<dialog>opened withshowModal(), or anaria-modal="true"element that is shown (checkVisibility({ visibilityProperty: true, opacityProperty: true })). Anaria-modalelement still in the page but closed (hidden,display: none,visibility: hidden, a closed popover, inside a closed<dialog>) leaves the keys with the game, and so does one fading out atopacity: 0.Keyboard.pressesis unchanged.What a game may need to change:
An
aria-modal="true"element left shown during play now takes every key. Hide it when its menu closes, or remove the attribute:A script that hides an
aria-modalmenu on Escape runs before awindowhost hears the key, so the game still gets that Escape. Prevent the key it handled:A game that merged a dialog's Escape with the game's Escape action (both arrived in one frame with focus on
<body>) now gets only the dialog's.Patch Changes
@typeonce/ritmo-devtools@0.25.0
Minor Changes
ritmo-devtools keyboard [--url <url>] [--route <file>] [--json]plays the game's page by keyboard in Chromium and fails on what breaks keyboard play: a menu open with focus outside it, Tab leaving an open menu, a control with no accessible name, Enter or Space not pressing the focused control, a press that drops focus to<body>, and a visible control the keyboard cannot reach. Each failure names the check, the screen, the control (role, name, selector), what was seen, and the fix; a check it cannot decide is printed as not checked, never as passed, and a screen on which nothing could be checked fails. Without--urlit serves the working directory with the game's own Vite config. A route file lists the screens to visit and how to reach them (key presses, clicks,waitFora named control, fixed waits); without one, the start page is the only screen. A loaded screen is walked as soon as it stops changing, and the real presses run on up to four pages at once, with any press that did not keep focus run again alone before it is reported. It presses controls for real to check focus, so a route marks what must not be pressed. It uses the optionalplaywrightandvitepeersverifyalready uses, at the same versions.Patch Changes
@typeonce/ritmo@0.25.0
Patch Changes
ritmoskill's UI playbook (ui-and-render.md) gains two steps for DOM controls and menus: build each control once and update it in place, never rewriting a region that holds one, and give it a name a test can find; a menu that stops play is a modal (showModal()on a<dialog>, or anaria-modalelement that moves focus in, keeps it there, and makes the page behind inert itself), whosecancelandcloseare intents, with apopover="manual"for a splash or wipe over it and a modal dialog of its own for a layer the player presses.ritmoskill's UI playbook (ui-and-render.md) checks a page with DOM controls withritmo-devtools keyboard, on a route through every screen that shows them.@typeonce/ritmo-math@0.25.0
Patch Changes
@typeonce/ritmo-netcode@0.25.0
Patch Changes
@typeonce/ritmo-pixi@0.25.0
Patch Changes
@typeonce/ritmo-render@0.25.0
Patch Changes
@typeonce/oxlint-plugin-ritmo@0.25.0
No changes in this release.
@typeonce/ritmo-tools@0.25.0
No changes in this release.