Skip to content

fix(settings): one keyboard stop per settings switch, with on/off - #37953

Merged
KiroCrewCaptain merged 1 commit into
mainfrom
crew/kiro-crew-rust/a11y-settings-switch
Nov 16, 2026
Merged

KiroCrewCaptain merged 1 commit into
mainfrom
crew/kiro-crew-rust/a11y-settings-switch

Conversation

@buluoray

@buluoray buluoray commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Each switch in Settings is one keyboard stop, and that stop tells a screen reader its name, whether it is on, and what it does.

Today every switch row is a button with the switch inside it. Tab stops on the row first. A screen reader reads "label, description, button" there, with no on or off, and Enter flips the setting anyway. Tab then stops a second time on the switch itself, which says on or off but not what the setting does.

One more switch has no name at all: "Include recent logs" in Report a problem reads as "switch, on".

Why it matters

A keyboard user presses Tab twice for every switch in Settings. A screen-reader user cannot tell from the first stop whether a setting is on, and can flip it from there without hearing the result. SettingsToggle is used 166 times in website/src, and apps get the same row through @kirocrew/app-sdk/ui.

Not a goal

  • Changing how a row looks, or what a mouse click on a row does.
  • Making label required on the shared Toggle type. Toggle is exported to apps through @kirocrew/app-sdk/ui, so that is a type change for every app and a separate decision.
  • The "?" tip beside a label. It stays its own stop.
  • Other keyboard gaps (sortable table headers, input error state, wide chat tables, message action buttons). Each has its own PR.

What changed (motivation → approach → change)

The row was drawn with Clickable, which makes it role="button" with a tab stop. The switch inside already had its own role, state and keys, so the row's button was a second control around the first.

The switch is now the only control, and the name beside it is its <label>. A label needs something it can be tied to, so the shared switch becomes a real <button role="switch">. The label is stretched over the row in CSS, so a click anywhere on the row still presses the switch. The row itself has no role, no tab stop and no click handler.

Part Before After
The row (website/src/components/settings.tsx) a button, in the Tab order, with its own click handler a plain container with no handler
The name in the row plain text the switch's <label>, covering the row
The switch (Toggle in website/src/components/ui.tsx) a div role="switch" a button role="switch"; same size, same keys
What the switch says name, on/off also the row's own text, then the caller's note
aria-busy while saving on the row and on the switch on the switch only
"Include recent logs" (website/src/components/ReportProblemModal.tsx) no name named after its label, described by its hint

The "?" tip, the switch, and any link or button inside a description sit above the label's click layer, so each is pressed itself. The row's text comes first in the description because that is the order on screen.

A comment in website/src/apps/ops-mission-control/SettingsPanel.tsx said the switch was a div that a label could not be tied to; it now says only what still holds.

Backwards compatibility

Compatible: SettingsToggle and Toggle keep their props (Toggle gains an optional id), the row keeps its data-setting-* anchors, and every press that flipped a switch before flips it once now. Two things change shape: the switch element is a <button> where it was a <div> (same role, name and state), and the row can no longer be focused or pressed with Enter; the switch, one Tab press later, already took the same keys.

Reader: website/src/hooks/useSettingHighlight.ts:settingAnchorSelector -- dashboard -- finds rows by data-setting-id / -key / -label, which stay on the row; settings.anchors.test.tsx
Reader: website/src/guide/findByName.ts:OPERABLE_ROLES -- dashboard -- matches [role="switch"], so a guide still finds the control by its name; src/guide tests pass
Reader: website/src/components/modelPickerKeyRouting.ts -- dashboard -- finds switches by [role="switch"], not by tag; the 17 model-picker test files pass
Reader: website/src/kirocrew-ui/index.ts:Toggle,SettingsToggle -- app -- same props; an app's switch is a button with the same role, and its row is one stop
Reader: website/src/test/AboutPanel.autoDownloadToggle.test.tsx -- dashboard -- found the row with closest('[role="button"]'); it now uses [data-setting-label]
Reader: website/src/test/previewSurfaces.test.tsx -- dashboard -- counts <button> elements as ways into a page; a switch is now a button, so it is left out by its role

Tests

Proof: not provable -- frontend test (prove.py runs Python only)

By hand instead: SettingsToggle.oneTabStop.test.tsx run on main (529da1e) fails 6 of its 9 tests; on this branch all 9 pass.

  • website/src/test/SettingsToggle.oneTabStop.test.tsx (new): two rows between two buttons take exactly one Tab press each; no button wraps the switch; the switch reports its state and "row text, then caller's note" as its description; a row with no text has no description; Space, Enter, a press on the label and a press on the switch each flip exactly once; the name is a <label> tied to the switch; a disabled row ignores a press on its label; a link in a description is pressed itself and does not flip the switch; Enter on the "?" tip opens the tip and does not flip; the Report a problem switch has a name and a description.
  • website/src/components/settings.anchors.test.tsx: the two tests that asserted "the row is a button" now assert the row has no role, no tab stop and no aria-busy, and that a press on the label reaches the switch.
  • InfoTip.settingsRow.test.tsx: presses the row's label where it pressed the row container.
  • NotificationsPanel.test.tsx, PrivacyPanel.recordMetrics.test.tsx, SessionEnvironmentsCard.test.tsx: these read aria-describedby as one id; they now expect the row's text first.
  • AboutPanel.autoDownloadToggle.test.tsx: finds the row by its anchor.
  • previewSurfaces.test.tsx: its count of buttons that lead into a page leaves switches out.

Determinism: seven of the eight changed test files, 20 runs with --sequence.shuffle and seeds 5053 to 6060 in steps of 53: 20 of 20 pass, 187 tests each. The eighth, previewSurfaces.test.tsx, passes 20 of 20 in its own order. Shuffled, a test this PR does not touch in that file ("lists Crew Members in the advertised surfaces on a default install") fails with seeds 5053 and 5106, and fails the same way on main at 529da1e with those seeds.

Related sets run locally: the repository's scoped runner (23 files, 477 tests) passes. Every test that imports a module drawing a Toggle or a SettingsToggle (337 files, 7045 tests): all pass. Tests that look up raw <button> elements or tag names outside that set (265 files): 260 pass; the other 5 files (SchedulePage.secrets, ChatInput.approval, DiffBlock.headerOwnership, PierreImpl.workerPool, CrewChatWindow) fail on this machine, the first four with the same counts on main without this change and the fifth on and off on both trees. tsc -p tsconfig.app.json and eslint on the changed files pass. The whole suite, the production build and Playwright were not run locally.

Manual verification

Chromium, driven by real key presses and mouse clicks, against a Vite dev server on loopback. The API is the repository's fixture stub (website/scripts/lib/stub-dashboard-api.mjs): no gateway, no model. Before is main at 529da1e, after is this branch.

Page Switch rows Stops on a row-button, before → after Tab stops on the page, before → after axe nested-interactive nodes, before → after
/settings/chat 14 14 → 0 109 → 95 14 → 0
/settings/display 3 3 → 0 58 → 55 3 → 0
/settings/privacy 2 2 → 0 44 → 42 2 → 0
/settings/about 1 1 → 0 45 → 44 1 → 0

Every way to press a row, on Settings > Chat. Each press flips the switch exactly once, before and after:

Press Before After
mouse on an empty part of the row flips flips
mouse on the name flips flips
mouse on the description flips flips
mouse on the switch flips flips
Space on the switch flips flips
Enter on the switch flips flips
mouse on the "?" tip opens the tip, no flip opens the tip, no flip
  • Every switch stop is still there (14, 3, 2, 1) and no switch on these pages is unnamed. The switch is 36×20 px with the knob at the same offset before and after.
  • On Privacy both switches now carry a description (0 before).
  • The other axe findings on these pages (aria-required-attr 1, landmark-unique 1, heading-order 1) are the same before and after.
  • Not checked: a real screen reader (NVDA, VoiceOver); Safari and Firefox; the light theme; a row with a link in its description in a browser (no Settings page draws one under the fixture stub; the unit test covers it); pages outside Settings that draw a Toggle, other than the Report a problem dialog.

Screenshots / video

Nothing changes at rest. Seven states, main on the left and this branch on the right, each pair compared pixel by pixel: rows at rest (two on, two off), a switch focused by Tab, a row hovered, rows with a description, a dimmed row, and the standalone switch in the Report a problem dialog, on and off. Six pairs are identical; the focused pair differs in one pixel on the ring's corner.

Seven before and after pairs of settings switches: at rest, focused, hovered, with a description, dimmed, and the Report a problem switch on and off

Full pages (1280×2200, nothing focused): Chat is pixel-identical before and after. Privacy and About differ only in a 2×24 px strip of the settings sidebar that also differs between two runs of the same build. Display differs in 45 pixels by at most 3 of 255 levels, on the edges of two controls this change does not touch (a side-rail item and the Interface picker); it repeats in every run and is not visible.

What does change is where keyboard focus lands. One frame per Tab press, both builds side by side:

Tab walk through Settings > Chat on main and on this PR: main stops on the whole row, then the tip, then the switch; this PR stops on the tip, then the switch

Recorded from 529da1e (before) and this branch's tree (after) · Chromium, real key presses and clicks · Vite dev server on loopback · fixture API stub, no gateway. Four switch rows take 12 presses before and 8 after.

Related Issues

Closes #37951

Sibling sweep

Swept: every <Clickable>…</Clickable> block in website/src (81 files) for <Toggle, <SettingsToggle or role="switch" inside it, and every literal role="button" with a switch in the next 40 lines
Swept: every <Toggle from components/ui (45) for a missing label, and every literal role="switch" (23) for a missing name
Sibling: website/src/components/ReportProblemModal.tsx:138 -- changed here
Sibling: website/src/components/Clickable.tsx -- not affected -- after this change no other Clickable block or role="button" in website/src wraps a switch

Pattern harvest

Rule candidate: lint
Pattern: a control with its own role (switch, button, link) rendered inside Clickable or role="button"

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@buluoray
buluoray requested review from a team and KiroCrewCaptain as code owners November 16, 2026 11:59
@buluoray
buluoray requested a review from bolichen97 November 16, 2026 11:59
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 16, 2026
@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of ec2dc6050fbf8dba38463460165cf1485252c75e — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: PASS

Nothing blocks. The fix removes the cause, which is the row being drawn as a Clickable button around a switch. The two deleted "row is a button" pins are named in the description, and their busy-state reason now holds on the switch.

What this change ships

Inventory (7 items) — 7 justified

Intent: let a keyboard or screen-reader user reach each Settings switch in one Tab stop that announces its name, its on/off state and what it does. FIX.

  1. A settings row is no longer its own Tab stop or button; only the switch is — justified
  2. Clicking a row's name (now a stretched <label>) still flips the switch — justified
  3. The switch's description now includes the row's own text before the caller's note — justified
  4. aria-busy moves off the row and onto the switch only — justified
  5. The shared Toggle is a <button role="switch"> and gains an optional id prop, which reaches apps through the SDK — justified
  6. The "Include recent logs" switch in Report a problem now has a name and a description — justified
  7. A comment in the ops-mission-control settings panel is reworded to drop the outdated claim that the switch is a div — justified

[FIRST-PRINCIPLES-REVIEWED] ec2dc60

Description read

[DESCRIPTION-READ] e4b6fe53d40908ddf960fe3ce9b77bd370a88683459195b0e78236df7442b295

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of ec2dc6050fbf8dba38463460165cf1485252c75e — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

No design concerns. The row is no longer a button wrapped around the switch: the switch is the one control and its label is stretched over the row, so a click anywhere on the row still flips it. Screenshots and a recording are attached.

Notes

  • When an app or caller puts Toggle inside its own <button> or <label>, the HTML is now invalid, or one press may flip the switch twice. No in-tree caller does this, but apps get Toggle through @kirocrew/app-sdk/ui, so the app-sdk docs should say the switch is now a <button>.

[DESIGN-REVIEWED] ec2dc60

Description read

[DESCRIPTION-READ] 1214b4659f013be7d98a5b50bc934d5f80e96d972aa17293e8f4734e51d93cf1

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS

UX-level review of ec2dc6050fbf8dba38463460165cf1485252c75e — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

UX-Verdict: PASS

Nothing blocks: the row looks the same, and the blind reader read the switch and its keyboard focus ring correctly ("clicking one flips it on or off -> sure -> yes").

Notes

  • The shot-02 caption says "a button, no on/off" and calls the tip a "?" while it is drawn as an "i". Both confused the blind reader. Captions that describe what the user hears and sees would make the before/after evidence clearer.

[UX-REVIEWED] ec2dc60

Description read

[DESCRIPTION-READ] 49e2883d9941f3f09f5292445e1bcd67070ed6287c748e0793fad700464094e0

That sha256 names everything this verdict read: the PR description, plus the 5 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed ec2dc6050fbf8dba38463460165cf1485252c75e — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] ec2dc60

Verdict parsed from the review's SHA-scoped output markers for commit ec2dc6050fbf8dba38463460165cf1485252c75e.

False positive or not applicable? A repository writer can comment:
/ai-review override fable ec2dc6050fbf8dba38463460165cf1485252c75e false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of ec2dc6050fbf8dba38463460165cf1485252c75e and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] ec2dc60

False positive or not applicable? A repository writer can comment:
/ai-review override gpt ec2dc6050fbf8dba38463460165cf1485252c75e false-positive: <reason, 20 to 500 characters>

@buluoray
buluoray force-pushed the crew/kiro-crew-rust/a11y-settings-switch branch from 4aec1eb to 40663b6 Compare November 16, 2026 12:06
@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Nov 16, 2026
@buluoray
buluoray force-pushed the crew/kiro-crew-rust/a11y-settings-switch branch from 40663b6 to 9d69921 Compare November 16, 2026 13:33
@buluoray

Copy link
Copy Markdown
Contributor Author

Rebased onto d2f22f2. The one red check on the previous head, Backend Tests (Windows) (6), was test/test_chat_runtime_tree_sharing.py::test_claude_leaves_each_per_session_field_out_of_the_key failing with ChatRuntimeKey.build() got an unexpected keyword argument 'shared_scratch'. It failed the same way on the previous base (9782f63) without this change, and #37945 fixed it on main. The website/ tree is unchanged by the rebase.

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 16, 2026
@buluoray
buluoray force-pushed the crew/kiro-crew-rust/a11y-settings-switch branch from 9d69921 to 4daf175 Compare November 16, 2026 14:37
@buluoray

Copy link
Copy Markdown
Contributor Author

self-added: yes
mechanism: the row's click handler is gone; the name is the switch's label, stretched over the row

  • Use a semantic label for the mouse-clickable switch row span=692504fc76d1

fixed in 4daf175: the row no longer has an onClick, a role or a tab stop. Toggle is a real <button role="switch">, the name beside it is <label htmlFor> tied to it, and the label is stretched over the row in CSS, so a click anywhere on the row presses the switch through the label.
Measured in Chromium on Settings > Chat, before and after: a mouse press on an empty part of the row, on the name, on the description and on the switch, and Space and Enter on the switch, each flip it exactly once; a press on the "?" tip opens the tip and flips nothing.
The row is still one Tab stop (14 row-button stops to 0 on that page), and axe nested-interactive stays at 0.

@buluoray

Copy link
Copy Markdown
Contributor Author

self-added: yes
mechanism: before and after stills of the switch in seven states, attached to the description

  • The changed switch rendering has no rendered evidence span=ae84afa386f4

fixed in 5d26657: the description now carries one attached image with seven before and after pairs from Chromium: four rows at rest (two on, two off), a switch focused by Tab, a row hovered, rows with a description, a dimmed row, and the standalone switch in the Report a problem dialog, on and off.
Each pair was compared pixel by pixel. Six are identical. The focused pair differs in one pixel on the ring's corner.
The same push fixes the comment in apps/ops-mission-control/SettingsPanel.tsx that still called the switch a div.

@buluoray

Copy link
Copy Markdown
Contributor Author

One red check on the previous head, Backend Tests (3.12, 5), was test/test_guide_ui_find.py::test_a_warm_catalog_validates_ui_find_without_reading_the_index. This PR changes only website/. The same shard passed on main at 529da1e and on #37977 and #37961 cut from it, and the node id fails the same way run alone on main without this change. Recorded in #37987.

A settings switch row was a button with the switch inside it. Every row took
two Tab presses, and the first stop read out as "label, description, button"
with no on or off.

The switch is now the only control. It is a real button, the name beside it
is its label, and the label is stretched over the row so a click anywhere on
the row still presses the switch. The row has no role, no tab stop and no
click handler. The switch carries the name, the on/off state and the row's
description (the row's own text first, then the caller's note).

"Include recent logs" in Report a problem had no name; it is now named after
its visible label and described by its hint.

Closes #37951
@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Nov 16, 2026
@buluoray
buluoray force-pushed the crew/kiro-crew-rust/a11y-settings-switch branch from 5d26657 to ec2dc60 Compare November 16, 2026 16:05
@buluoray

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in website/src/components/ (SortableHeader.tsx, ChatPane.tsx, MarkdownRenderer.tsx, RedactionCards.tsx, WidgetFrame.tsx, blockedLinkRecords.ts) since this head went green (529da1e -> 028c39d); CI re-running.

The commit is unchanged (git range-diff reports =): 5d26657c28f -> ec2dc6050fb. No conflict. After the rebase the 9 related test files pass locally (230 tests), and the frontend blocking-rule greps pass.

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: passed Eligible automated validation passed for the current revision labels Nov 16, 2026
@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Nov 16, 2026
@KiroCrewCaptain

Copy link
Copy Markdown
Collaborator

Code change approver recommendation: Approve

Why: the decider estimates a 10% chance that this change introduces a defect, within the 12% limit for approving on its own, and every check passes.

The PR replaces the Clickable row around each settings switch with a plain div. The row's name becomes a stretched over the row, and the shared Toggle becomes a . I verified the following in the code. Key handling cancels the button's own press, so Enter and Space flip the switch once. The inert guard stays in onClick, so a disabled or busy switch ignores clicks that arrive through the label. The tip, the switch, and links and buttons in descriptions are positioned above the label's click layer. No in-tree caller wraps Toggle in a label, button or clickable row, and every SettingsToggle description I traced is text or a badge. Readers of data-setting-* anchors, [role=switch] lookups, and handlers that skip clicks on buttons still work. The new test file covers the behaviour, the updated tests match the new describedby order, and CI is fully green. Minor notes: print-preview CSS hides buttons, the SDK docs should mention the element change, and only Chromium was checked by hand.

An automated recommendation, not a review: a maintainer still decides. It approves on its own only when the estimated chance of a defect is at most 12% and the change has at most 400 changed lines. Decider v3c (217fe607) · commit ec2dc6050f · 306 changed lines. If this recommendation is wrong, reply here: replies are how the approver is evaluated.

@KiroCrewCaptain
KiroCrewCaptain enabled auto-merge (squash) November 16, 2026 17:40

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving. Checks on ec2dc60:

  • The settings row is no longer a button wrapped around a switch. A <label htmlFor> stretched over the row keeps the whole row clickable, with one tab stop and one handler.
  • inert still blocks a label click on a busy row.
  • All 33 Toggle callers sit in flex or grid parents, and none is nested in a label or button.
  • type="button" keeps the switch from submitting a form.
  • Six of the nine new tests fail on main.
  • PR Readiness is green.

Done well: the fromHint and stopPropagation workaround is deleted, not added to.

  • Optional: drop Toggle's onKeyDown (ui.tsx:507) and let the native button turn Space and Enter into a click. As written, each press flips once only where cancelling the Space keydown also cancels the click on keyup. That holds in Chromium, but Firefox and Safari were not checked.
  • Optional: pin type="button" with a test that clicks a switch inside a <form onSubmit> and expects no submit.
  • Optional: say in the app-kit docs that Toggle is now a <button> and must not sit inside another button or a label. Also correct the body: the unit test does not prove that a link inside a description stays clickable in a browser.

@KiroCrewCaptain
KiroCrewCaptain merged commit ab3a69d into main Nov 16, 2026
99 checks passed
@KiroCrewCaptain
KiroCrewCaptain deleted the crew/kiro-crew-rust/a11y-settings-switch branch November 16, 2026 17:41
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 16, 2026
KiroCrewCaptain added a commit to KiroCrewCaptain/kirocrew-app-ops-mission-control that referenced this pull request Nov 17, 2026
Ports every change the built-in got after the af94fac51f sync, so an
adopted record keeps what a built-in user has:

- the ledger's episode import into Crew's memory is skipped while a
  memory provider replaces it (kirodotdev/KiroCrew#37218), through a
  new memory_provider row of the host table; a gateway without the
  resolver indexes nothing
- the Japanese strings without the stray source line breaks
  (kirodotdev/KiroCrew#38368)
- two comment-only changes (kirodotdev/KiroCrew#37469,
  kirodotdev/KiroCrew#37953)

The test pin and docs/spec.md move to KiroCrew main 2e2503671f, and the
fixtures follow the host's scrubber (kirodotdev/KiroCrew#37408) and the
gh PATH probe pin (kirodotdev/KiroCrew#37597). PORTING.md has a row per
core change and records that the pin needs App Kit level 10, where the
agent's file-tool gate fences the credentialMasks directory
(kirodotdev/KiroCrew#37459).

Part of kirodotdev/KiroCrew#26967.

Co-authored-by: KiroCrewCaptain <312312717+KiroCrewCaptain@users.noreply.github.com>
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.

Settings switch rows take two Tab presses and the first stop never says on or off

2 participants