Skip to content

Version Packages - #233

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

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.actions leaves 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 was preventDefault-ed, so the dialog did not close.

    A modal is now open when the key's document holds a <dialog> opened with showModal(), or an aria-modal="true" element that is shown (checkVisibility({ visibilityProperty: true, opacityProperty: true })). An aria-modal element 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 at opacity: 0. Keyboard.presses is 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:

      menu.hidden = true // or menu.hidePopover(), or menu.removeAttribute("aria-modal")
    • A script that hides an aria-modal menu on Escape runs before a window host hears the key, so the game still gets that Escape. Prevent the key it handled:

      document.addEventListener("keydown", (event) => {
        if (event.key === "Escape" && menu.matches(":popover-open")) {
          event.preventDefault()
          menu.hidePopover()
        }
      })
    • 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

  • Updated dependencies [cd6bb2e]
  • Updated dependencies [989049f]
    • @typeonce/ritmo@0.25.0

@typeonce/ritmo-devtools@0.25.0

Minor Changes

  • 989049f: 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 --url it 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, waitFor a 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 optional playwright and vite peers verify already uses, at the same versions.

Patch Changes

  • Updated dependencies [cd6bb2e]
  • Updated dependencies [989049f]
    • @typeonce/ritmo@0.25.0
    • @typeonce/ritmo-netcode@0.25.0

@typeonce/ritmo@0.25.0

Patch Changes

  • cd6bb2e: The ritmo skill'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 an aria-modal element that moves focus in, keeps it there, and makes the page behind inert itself), whose cancel and close are intents, with a popover="manual" for a splash or wipe over it and a modal dialog of its own for a layer the player presses.
  • 989049f: The ritmo skill's UI playbook (ui-and-render.md) checks a page with DOM controls with ritmo-devtools keyboard, on a route through every screen that shows them.

@typeonce/ritmo-math@0.25.0

Patch Changes

  • Updated dependencies [cd6bb2e]
  • Updated dependencies [989049f]
    • @typeonce/ritmo@0.25.0

@typeonce/ritmo-netcode@0.25.0

Patch Changes

  • Updated dependencies [cd6bb2e]
  • Updated dependencies [989049f]
    • @typeonce/ritmo@0.25.0

@typeonce/ritmo-pixi@0.25.0

Patch Changes

  • @typeonce/ritmo-render@0.25.0

@typeonce/ritmo-render@0.25.0

Patch Changes

  • Updated dependencies [cd6bb2e]
  • Updated dependencies [989049f]
    • @typeonce/ritmo@0.25.0

@typeonce/oxlint-plugin-ritmo@0.25.0

No changes in this release.

@typeonce/ritmo-tools@0.25.0

No changes in this release.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from b523baf to b848041 Compare November 16, 2026 17:57
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from b848041 to 3c021b6 Compare November 17, 2026 05:43

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants