chore(deps): bump the production-dependencies group across 1 directory with 3 updates

[dependabot]

Bumps the production-dependencies group with 3 updates in the / directory: @vectojs/core, @vectojs/devtools and @vectojs/ui.

Updates @vectojs/core from 1.11.1 to 1.17.1

Commits

• effabed chore(release): @​vectojs/core@​1.17.1, @​vectojs/ui@​2.3.0 (#222)
• de170fe feat(ui): add Button.disabled and Input/TextArea required+invalid (#221)
• b384024 fix(core): split the WASM loader's byte and network paths (CodeQL 16) (#220)
• 02c8650 chore(release): @​vectojs/core@​1.17.0 (#219)
• d25cbe2 perf(core): split the animation gate per driver kind (#218)
• 49a7b3c fix(core): revalidate WASM views after a shared-instance memory growth (#217)
• 493370a build(core): gate the f32 bench kernel behind a Cargo feature (#216)
• 6a0e942 fix(core): validate capacity and run tables in the raw WASM ABI (#215)
• 447eb4f perf(core): share one WASM instance per Scene across all accelerators (#214)
• f9d4066 chore(release): @​vectojs/core@​1.16.3, @​vectojs/ui@​2.2.0 (#213)
• Additional commits viewable in compare view

Updates @vectojs/devtools from 0.4.3 to 0.6.0

Updates @vectojs/ui from 1.11.6 to 2.3.1

Changelog

Sourced from @​vectojs/ui's changelog.

2.3.1

Patch Changes

• ddbe993: Trap Tab inside an open Modal.

  Modal projected role="dialog" with aria-modal="true" and moved focus in on open, but nothing constrained the browser's tab order — aria-modal tells assistive technology that outside content is inert, it does not stop Tab from leaving. Measured in real Chrome and Firefox: the first Tab after opening landed on a background control and successive presses walked the whole page behind the dialog, so a keyboard user was operating things they could not see.

  Tab and Shift+Tab now cycle within the dialog's own focusable elements, entering at the correct edge when focus arrives from outside. Escape-to-close and focus restoration already worked and are now covered by tests too.

  The trap is removed on close() and on destroy(), so a modal discarded without closing cannot leave a document listener trapping Tab for the page's lifetime.

• 8b3f10e: RadioGroup now handles Home and End.

  Arrow keys already moved within the group, but Home/End did nothing — focus stayed put. The ARIA radiogroup pattern requires both, and Tabs already implemented them, so the group was the odd one out.

  Home selects the first enabled option and End the last, scanning inward so a disabled option at either edge does not swallow the key. Landing on a disabled radio would be worse than not moving.

2.3.0

Minor Changes

• de170fe: Add Button.disabled and Input/TextArea required + invalid.

  A11yAttributes has supported all three since the projection layer was written, but no component wired them, so an app could not express "this control is unavailable" or "this field failed validation" at all — visually or semantically. Found while building the a11y conformance fixture, which had to stand these in with local entities.

  new Button("Save", { disabled: true });
  new Input({
    width: 220,
    placeholder: "Email",
    required: true,
    invalid: true,
  });

... (truncated)

Commits

• 502cfcb chore(release): @​vectojs/ui@​2.3.1 (#227)
• 2017710 test(ui): pin visual-vs-semantic state parity across components (#226)
• 8b3f10e test(ui): audit per-role keyboard protocols; add RadioGroup Home/End (#225)
• 31ba928 test(ui): cover TreeView, Table and ContextMenu in the conformance suite (#224)
• ddbe993 fix(ui): trap Tab inside an open Modal (#223)
• effabed chore(release): @​vectojs/core@​1.17.1, @​vectojs/ui@​2.3.0 (#222)
• de170fe feat(ui): add Button.disabled and Input/TextArea required+invalid (#221)
• f9d4066 chore(release): @​vectojs/core@​1.16.3, @​vectojs/ui@​2.2.0 (#213)
• 75b06a3 test: a11y conformance suite, gate symmetry, and two nameless roles fixed (#212)
• 65a61b4 chore(release): version all @​vectojs packages (#201)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions