[material-ui] Add theme.focusVisible opt-in keyboard focus ring by siriwatknp · Pull Request #48743 · mui/material-ui

siriwatknp · 2026-06-30T12:00:15Z

Docs: https://deploy-preview-48743--material-ui.netlify.app/material-ui/customization/focus-visible/

Summary

Implements the opt-in, themeable keyboard focus ring from RFC #48718.

A single theme key, theme.focusVisible, styles the Mui-focusVisible state — the keyboard-focus state ButtonBase already tracks — across ButtonBase and every component that builds on it, with no per-app wiring. It's aimed at teams that turn off the Material Design ripple (disableRipple) and are otherwise left with no visible keyboard-focus indicator (a WCAG 2.4.7 gap).

createTheme({ focusVisible: true });
// or customize — merges over the curated default:
createTheme({ focusVisible: { outlineColor: '#9c27b0', outlineOffset: 3 } });

Value	Behavior
`undefined`	No ring — default, fully non-breaking (zero visual diff)
`true`	Curated ring: `2px solid`, `primary.main`, `2px` offset
object (`FocusVisible` = `React.CSSProperties`)	Merged over the curated default
`false`	Reserved kill-switch for the deferred auto-on fallback

Rendered with CSS outline (survives Windows High Contrast / forced-colors, no layout shift, no collision with the box-shadow elevation Button/Fab already animate). Coverage:

Free via ButtonBase — Button, IconButton, Fab, and any custom ButtonBase consumer.
Clip-prone families inset the ring so a scroller/overflow ancestor can't cut it — Tab, MenuItem, ListItemButton, CardActionArea, BottomNavigationAction, and the Autocomplete option (a plain <li>).
Slot-drawn controls put the ring where it reads, not on the padded hit area — Checkbox/Radio (icon svg), Switch (track), Slider (thumb), Rating (active icon + empty-value label), Link (component="button").

Ships with an exported FocusVisible type, a guide at customization/focus-visible, and the /experiments/focus-ring prototype.

For Reviewers

Hide whitespace when review.

Color resolution lives in three places, one per theme mode. The geometry (outlineWidth/Offset/Style + inset-var wiring) is shared by resolveFocusVisible in styles/focusVisible.ts; only the default outlineColor differs:

createTheme({ focusVisible: true })
- Resolved in: createThemeNoVars.js
- Default outlineColor: resolved hex off palette.primary.main
- Dark mode: — (single scheme)
createTheme({ focusVisible: true, colorSchemes: { light, dark } })
- Resolved in: createThemeNoVars.js (default scheme, top-level) + createTheme.ts (per-scheme copy)
- Default outlineColor: each scheme's own primary.main
- Dark mode: swaps on useColorScheme mode change
createTheme({ cssVariables: true, focusVisible: true })
- Resolved in: createThemeWithVars.js
- Default outlineColor: var(--mui-palette-primary-main)
- Dark mode: adapts at the CSS level

Scenario 2 needs extra care: without CSS vars the provider switches schemes by shallow-merging colorSchemes[mode] onto the theme and re-rendering (no CSS var to adapt). So createTheme.ts gives each scheme its own resolved focusVisible, and that same merge swaps the outline color per mode — exactly as it does palette. Scenario 3 needs no per-scheme copy because the palette var adapts on its own.

Inset contract (private CSS vars). Clip-prone roots spread applyInsetFocusVisible, which sets --_focusVisible-offset (flips the outline-offset sign, outset→inset) and --_focusVisible-behavior (makes a user boxShadow inset). wireFocusVisibleVars bakes the resolved offset/box-shadow to read those vars, so a component never has to know the ring width — the same customized ring insets or not per component with no field mapping.

CSS variables. focusVisible is skipped from var generation (shouldSkipGeneratingVar) and kept inline: hoisting it to :root would resolve the per-component private vars where they're unset, breaking the inset. Inline + palette var keeps both the inset and the scheme-reactive color working.

ButtonBase gate. The root ring is gated by a private internalDisabledThemeFocusVisible prop (default false); the whole variant is a no-op when theme.focusVisible is unset. SwitchBase sets it true so Checkbox/Radio/Switch suppress the root ring and draw on their slot instead.

styles/focusVisible.ts. One module holding the shared resolver and the inset contract. Named exports: resolveFocusVisible / extractFocusVisibleInput (feed the three resolution sites), wireFocusVisibleVars, outsetFocusRing, applyInsetFocusVisible, and applyChildrenFocusVisible (colored surfaces set the ring's shadow slot through it) — the private var names stay module-internal.

Tests. createTheme.test.js (normalization + per-scheme + vars) and createTheme.spec.ts (types); computed-style tests across ButtonBase, Tab, Checkbox, Radio, Switch, Slider, Rating, Link, Autocomplete, Fab, Button; ThemeProvider.test.tsx drives setMode('dark') and asserts the outline color follows the active scheme. Visual-regression fixtures under test/regressions/fixtures/FocusVisible/ cover the ring across the inset families, selection controls, the Autocomplete option, and forced-colors mode. The fixtures render already focus-visible (they force the Mui-focusVisible class on mount — faithful, since the ring is class-driven, not :focus-visible-driven), so the standard screenshot loop captures each in one shot with no redundant un-focused baseline.

Colored surfaces (in scope). Saturated containers (color-variant AppBar, filled Alert, SnackbarContent) set a private --_focusVisible-shadow var (0 0 0 4px background.default); the curated ring's box-shadow slot (var(--_focusVisible-shadow, 0 0)) consumes it, drawing a background-colored halo behind the outline so the indicator keeps contrast there. A custom boxShadow in theme.focusVisible replaces that slot — surface contrast is then the author's call.

RFC: #48718

Render an outline focus ring on Mui-focusVisible: - auto fallback when disableRipple removes the ripple focus indicator - opt-in via theme.focusRing (outline CSSProperties), ripple-independent - theme.focusRing: false hard-disables the ring Experiment: design in CONTEXT.md + docs/adr, demo at docs/pages/experiments/focus-ring.tsx.

- Normalize focusRing at theme creation (true -> curated object, object merges over) - Vars theme: curated color = palette var (scheme-reactive); numeric -> px - Single Mui-focusVisible rule on ButtonBase; drop auto-on variants block - Widen type to boolean | React.CSSProperties; update createTheme type tests

Replace old auto-on/fallback demo with the must-tier playground (M1-M5): preset switcher, light/dark, all ButtonBase-derived + bare ButtonBase, keyboard journey + focused readout, elevation/disabled edge callouts.

… controls + gallery) Rework to match the agreed ASCII: header band (title, keyboard hint, live focused readout, light/dark top-right); sticky left CONTROLS (preset radios); right GALLERY. Layout-only — gallery + theme logic unchanged.

…ring) Row-by-row CSS Grid (label | component), two labelled buckets. Inner-ring components (Tab, MenuItem, ListItemButton) get an inset ring (outlineOffset -2) via their own ThemeProvider, so a scrollable container can't clip them.

Add every ring-bearing family to the right bucket (verified offsets): outer (+2) — ButtonGroup, Chip, Checkbox, Radio, Switch, Stepper, Pagination; inner (-2) — AccordionSummary, BottomNavigation, TableSortLabel.

…flow clip) Visual verify caught it: CardActionArea sits in a Card with overflow:hidden, so an outer ring (+2) is clipped to nothing. Inset (-2) draws inside the card -> visible.

- add utils/toPx (number->px, pass-through for strings/vars) - Tab, MenuItem, ListItemButton, BottomNavigationAction, CardActionArea: inset focus ring on Mui-focusVisible (outlineOffset calc(-1 * focusRing.outlineWidth)), so one app-level theme.focusRing renders correctly inside scroll/overflow-clipped containers - Switch: SwitchRoot overflow -> visible when focusRing set (else hidden) to un-clip the ring - docs experiment: single ThemeProvider; inset now from component source; move AccordionSummary/TableSortLabel to outer-ring (verified no clip)

- createTheme.test.js: focusRing normalization (true/object/transparent/boxShadow/ false/undefined) + vars theme (palette var, numeric->px fallback) - ButtonBase.test.js: ring on/off, recolor merge, transparent opt-out (browser-gated) - Tab.test.js: inset outlineOffset -2px on focus-visible (browser-gated) - Switch.test.js: root overflow visible when focusRing set, else hidden (browser-gated) - utils/toPx.test.ts

- docs/data/material/customization/focus-ring/: focus-ring.md + demos FocusRingDefault, FocusRingCustomization (js + tsx) - route docs/pages/material-ui/customization/focus-ring.js - pages.ts: nav entry under Customization (newFeature)

- N1 pointer walk (Prev/Next + n/total) via .Mui-focusVisible shim; real-Tab drops it (no double-ring) - N2 custom focusRing JSON editor (overrides preset; invalid -> inline error) - N3 CSS variables on/off toggle - N4 resolved theme.focusRing panel - N5 edge callouts: overflow:hidden clip + forced-colors

…led) - resolve the ring root via closest('.MuiButtonBase-root') so Checkbox/Radio/Switch get .Mui-focusVisible on the SwitchBase root, not the inner input - skip disabled targets in the walk (isRingDisabled: Mui-disabled / aria-disabled / input.disabled) - collect targets from document (data-ring-target lives only in the gallery) instead of a ref that resolved null; drop the dead galleryRef

- remove CONTEXT.md (experiment-only glossary, not for upstream) - prettier format experiment page + Switch test

code-infra-dashboard · 2026-06-30T12:02:47Z

Deploy preview

Bundle size

Bundle	Parsed size	Gzip size
@mui/material	🔺+4.35KB^(+0.83%)	🔺+962B^(+0.63%)
@mui/lab	0B^(0.00%)	0B^(0.00%)
@mui/private-theming	0B^(0.00%)	0B^(0.00%)
@mui/system	0B^(0.00%)	0B^(0.00%)
@mui/utils	0B^(0.00%)	0B^(0.00%)

Details of bundle changes

Check out the code infra dashboard for more information about this PR.

…ing to non-ButtonBase controls - API rename: theme.focusRing -> theme.focusVisible (key, --mui-focusVisible-* vars, FocusVisible type, docs page, demos, experiment page) - Extend curated ring beyond ButtonBase: Slider (thumb), Link (covers Breadcrumbs links), Autocomplete option (inset). Select items already covered via MenuItem. - Experiment page: add 'own focus' bucket (Slider/Link/Breadcrumbs) + Select/Autocomplete in inner-ring - Tests: browser-gated focus-visible tests for Link/Slider/Autocomplete

…0002 to v1 opt-in - createThemeWithVars: resolve focusVisible from options+merge args (mirrors createThemeNoVars) so createTheme({cssVariables:true},{focusVisible:true}) normalizes instead of leaving a raw boolean - rewrite adr/0002: v1 is opt-in only, auto-on fallback deferred; document reserved false + scope-by-mechanism

…her components Use the root-level ...(theme.focusVisible && {...}) pattern like Slider/Tab instead of a props:()=>Boolean variant. Gate the component=button variant outline:auto to the non-themed case so the curated ring no longer relies on variant source order. Add a button-Link regression test.

…le-alignment)

Switch applies components.MuiButtonBase.defaultProps.disableRipple app-wide to the preview theme. Demonstrates WCAG 2.4.7: ripple off + ring preset off leaves keyboard focus with no indicator; the curated ring restores it.

…onGroup - drop helper text + wrapper div so the switch aligns with the CSS-variables one - also set MuiButtonGroup defaultProps: ButtonGroup re-broadcasts disableRipple (default false) via context, shadowing the MuiButtonBase default

LukasTy · 2026-08-06T07:47:21Z

I lean to the latter.

Agreed, I think more spacing looks way better. 👍

…to show full demo source

silviuaavram · 2026-08-06T07:52:41Z

I also like the second better.

…s unclickable; ring fits root padding) + hit-area regression test; skip behavior-var prefix on standalone box-shadow keywords; drop redundant focusVisible guard in Button/Fab; assert Mui-focusVisible class in Checkbox/Fab tests

…s constants instead of literal

…ract test (true case), key-level asserts elsewhere

…o longer conditional)

Signed-off-by: Siriwat K <siriwatkunaporn@gmail.com>

siriwatknp · 2026-08-06T10:35:44Z

Latest changes

Complete colored background surface support with the proposed solution, docs added.
Update Tab to have 3x inset
Fix Switch overflow issue (revert back to original implementation)

Ready for another review

LukasTy · 2026-08-06T12:16:03Z

Nice work, the Tabs look way better now.

Below is a curated Claude Opus 5 review

Fixed since the last round

Switch hit area. I probed the bare Switch again. No dead points in any state.
Standalone box-shadow keywords. boxShadow: 'none' stays none.
The curated default keeps the Button elevation and the Slider halo. Button, Fab and Slider compose both shadows.
Colored surfaces are a good addition. They work for outset and inset components. A Tab inside an AppBar mirrors the halo inward and still forms a two-color indicator.

Still broken

Switch track colors. All three states are unchanged. color="default" checked renders 0.38; it rendered 0.5 before, so a checked switch now matches an unchecked one. Vars mode disabled renders 0.38 against an expected 0.12. Vars mode checked plus disabled renders 0.38 against an expected 0.12.
The theme resolution reads back its own output. Recompose a colorSchemes theme: the dark ring becomes #1976d2 while the dark palette stays #90caf9. A palette in a merge argument does not change the ring. extractFocusVisibleInput takes the last argument instead of a deep merge, so vars mode drops outlineStyle: 'dashed' and no-vars mode keeps it. The same input gives a different ring for each mode.

Follow-ups

ButtonGroup with variant="contained" hides one edge of the ring. The next sibling paints over it.
Checkbox and Radio with a custom icon that is not an svg show no ring. The selector svg:first-of-type matches nothing.
disableElevation plus the documented box-shadow-only recipe leaves no indicator. The outline is transparent in that recipe and Button.js:292 sets box-shadow: none. This is narrow and needs one line.
The docs info box still says the ring shadow replaces the Button elevation. Button and Fab now compose both. Update that note.
Button.js:136 and Fab.js:84 use theme.shadows[6]. The line below uses (theme.vars || theme).shadows[6]. The curated default always sets a boxShadow, so the first branch always runs and the second line is dead.
applyChildrenFocusVisible is not gated on theme.focusVisible. Every applyInsetFocusVisible call site is gated.
The Tab inset multiplier scales with a custom offset. applyInsetFocusVisible(3) gives -6px by default and -12px with outlineOffset: 4. Confirm that this depth is intended.
outsetFocusRing still uses 'var(--__,)'. initial is the correct idiom.

Tests

No test asserts the ring's computed outline. I grepped outlineStyle and outlineWidth across the package and found one unrelated Dialog hit. Switch and Button contain zero focusVisible tests, and those two components hold three of the confirmed defects. The VRT fixtures cover no disabled state, no color="default", and no colored surface. Every defect above therefore passes CI.

…ackDisabled (0.12, was switchTrack 0.38); add default-color checked 0.5 rule before disabled so the combo dims

… disabled/checked+disabled 0.12

…ounds

…o playgrounds" This reverts commit aed11d7.

…rge wrapper), resolve against merged palette, recompose re-derives per-scheme color via baked-default check; TDD tests

siriwatknp · 2026-08-10T07:24:57Z

Still broken

Both are fixed now.

Switch track colors — fixed in 3186084. Used the wrong variable, opacity.switchTrack instead of opacity.switchTrackDisabled, and the default color missed a dim rule for checked. Added 2 VRT fixtures with all six track states so each one has a golden screenshot now (db5c775).
Theme resolution — fixed in 4a5ddc0. All three cases had the same cause: focusVisible was not merged the same way as the rest of the theme. Now it deep-merges like every other theme key, and the ring color reads the final palette — so a palette in a merge argument recolors the ring, and createTheme(theme, overrides) keeps the ring color per scheme.

One known limit: recomposing a theme AND changing its color source (palette or cssVarPrefix) in the same call keeps the previous ring color. Workaround: pass focusVisible: true again in that call. I think fixing it properly is not worth it for v1 — happy to revisit if you disagree.

…-aware shadows[6] compose (Button/Fab), gate applyChildrenFocusVisible on theme.focusVisible, outset behavior var uses initial, docs compose note

siriwatknp · 2026-08-10T07:43:07Z

On the follow-ups — 5, 6, 7, 8, 10 are addressed in d469618.

Open to ideas, but I accept this limitation for now.
Widening the selector is risky — *:first-of-type rings the hidden input (it is the first child), and a type list like :is(svg, div, span) rings the ripple too. So svg only for v1; a non-svg icon can add the ring with one styleOverrides line. Open to a different direction if you see one.
Confirmed a bug — disableElevation reset the focus box-shadow to none, which killed the box-shadow-only recipe. Now it keeps the ring shadow.
Docs note updated — Button/Fab compose both shadows, not replace.
Half right — the compose branch is now vars-aware. The second line is not dead though, it runs when focusVisible is unset.
Gated all three call sites on theme.focusVisible.
Yes, intended — the inset depth follows the ring geometry.
Done — initial works, verified computed styles in the browser runner.

…ppBar rows with matched geometry, secondary indicator

LukasTy · 2026-08-10T12:37:54Z

Awesome work on fine tuning edge-cases. 👌
Everything checks out.

One note regarding the Switch component states VRT: on first check I got confused with same labels and different visuals.
Nitpick, but could be worth adding an extra word/label for the default colored states to differentiate from the actual "default" primary color.

Remaining

ButtonGroup variant="contained" hides one edge of the ring. It's not a dealbreaker, just a bit suboptimal result.
This case essentially seems similar to the other colored surfaces, so, we could consider similar approach. However, it might be a bit too extreme.
Have you considered applying z-index: 1 on the focused item?
Checkbox and Radio with a non-svg icon. Your selector reasoning is correct: *:first-of-type rings the hidden input. One selector does work: & > *:not(input):not(.MuiTouchRipple-root). I'm fine keeping it as is for the initial release, but maybe we could document this possible "gotcha"?

Nits

The known theme limit needs to reach the docs. A recompose plus a palette change in one call keeps the old ring color. I reproduced it. That limit lives only in a PR comment today, so a user meets a wrong-colored ring with no warning.
Two reviewer asks are still open in the docs. Silviu asked for a section about components that need manual changes; the page has zero mentions of the focus tint. Marija asked to show how to remove the Slider overlay; the demo still renders a plain Slider.

siriwatknp · 2026-08-11T08:41:27Z

For ButtonGroup variant="contained", z-index would not help because the color (primary.main) is the same.

… the focus indicator

LukasTy · 2026-08-11T08:46:50Z

For ButtonGroup variant="contained", z-index would not help because the color (primary.main) is the same.

Indeed, for the same color outline it wouldn't, but it would resolve the issue itself if someone decides to go with customized color.
P.S. The same issue is present in the ToggleGroup.

siriwatknp · 2026-08-11T08:58:12Z

Screen.Recording.2569-08-11.at.15.56.48.mov

Added z-index looks better for all of the colors.

siriwatknp added 14 commits June 10, 2026 10:26

Merge branch 'master' into exp/focus-ring

c350d37

[docs] focus-ring experiment page: presets, light/dark, component matrix

5f86ca7

Replace old auto-on/fallback demo with the must-tier playground (M1-M5): preset switcher, light/dark, all ButtonBase-derived + bare ButtonBase, keyboard journey + focused readout, elevation/disabled edge callouts.

[docs] focus-ring experiment: move CardActionArea to inner-ring (over…

3a42b01

…flow clip) Visual verify caught it: CardActionArea sits in a Card with overflow:hidden, so an outer ring (+2) is clipped to nothing. Inset (-2) draws inside the card -> visible.

[docs] focus-ring: customization page (Phase 5)

502ac86

- docs/data/material/customization/focus-ring/: focus-ring.md + demos FocusRingDefault, FocusRingCustomization (js + tsx) - route docs/pages/material-ui/customization/focus-ring.js - pages.ts: nav entry under Customization (newFeature)

[docs] focus-ring: drop experiment glossary + prettier

df3d90e

- remove CONTEXT.md (experiment-only glossary, not for upstream) - prettier format experiment page + Switch test

Merge remote-tracking branch 'upstream/master' into focus-ring-v1

682cb21

siriwatknp added the RFC Request For Comments. label Jun 30, 2026

siriwatknp changed the title ~~[ButtonBase] Add theme.focusRing for a themeable keyboard focus ring~~ [WIP][Prototype] Add theme.focusRing for a themeable keyboard focus ring Jun 30, 2026

siriwatknp added 2 commits June 30, 2026 22:00

fix ci

a47620f

fix ci

7c393ce

siriwatknp mentioned this pull request Jul 1, 2026

[RFC] theme.focusVisible — opt-in keyboard focus ring #48718

Open

siriwatknp changed the title ~~[WIP][Prototype] Add theme.focusRing for a themeable keyboard focus ring~~ [WIP][Prototype] Add theme.focusVisible for a themeable keyboard focus ring Jul 2, 2026

siriwatknp added 7 commits July 2, 2026 21:35

Merge remote-tracking branch 'upstream/master' into focus-ring-v1

798c0e9

fix ci: adr/0002 table explicit column alignment (remark-lint-mui-tab…

857bc4a

…le-alignment)

wire Rating active icon into theme.focusVisible; add demo row + tests

ef32a69

siriwatknp added 2 commits August 6, 2026 14:50

docs: colored-surface demo centered spacing; drop .tsx.preview files …

a6430f1

…to show full demo source

Merge remote-tracking branch 'upstream/master' into focus-ring-v1

9a7ee5b

siriwatknp added 6 commits August 6, 2026 16:37

Merge branch 'master' of github.com:mui/material-ui into focus-ring-v1

e9413f6

remove comment

1a1835a

tests: focus-visible class assertions via fabClasses/buttonBaseClasse…

573ae9c

…s constants instead of literal

tests: slim focusVisible resolver tests — one CURATED deep-equal cont…

f6d9436

…ract test (true case), key-level asserts elsewhere

tests: drop Switch focusVisible overflow + hit-area tests (overflow n…

db6c20e

…o longer conditional)

siriwatknp commented Aug 6, 2026

View reviewed changes

Comment thread packages/mui-material/src/ButtonBase/ButtonBase.js Outdated

siriwatknp added 2 commits August 6, 2026 17:29

Apply suggestion from @siriwatknp

7606a61

Signed-off-by: Siriwat K <siriwatkunaporn@gmail.com>

tests: inline CURATED into its only remaining usage

4a21f0b

siriwatknp added 5 commits August 10, 2026 11:39

Switch focusVisible track colors: vars disabled opacity uses switchTr…

3186084

…ackDisabled (0.12, was switchTrack 0.38); add default-color checked 0.5 rule before disabled so the combo dims

VRT: Switch track-state fixtures (vars off/on) — default checked 0.5,…

db5c775

… disabled/checked+disabled 0.12

experiments: switch-hit-area + focus-visible-regressions repro playgr…

aed11d7

…ounds

Revert "experiments: switch-hit-area + focus-visible-regressions repr…

bf28205

…o playgrounds" This reverts commit aed11d7.

focusVisible resolution: deep-merge input across options+args (deepme…

4a5ddc0

…rge wrapper), resolve against merged palette, recompose re-derives per-scheme color via baked-default check; TDD tests

siriwatknp force-pushed the focus-ring-v1 branch from 2f227ad to 4a5ddc0 Compare August 10, 2026 07:24

focusVisible follow-ups: disableElevation keeps ring box-shadow, vars…

d469618

…-aware shadows[6] compose (Button/Fab), gate applyChildrenFocusVisible on theme.focusVisible, outset behavior var uses initial, docs compose note

docs: rewrite FocusVisibleBoxShadow demo — inline structure, Card + A…

3134103

…ppBar rows with matched geometry, secondary indicator

docs: caveat — Checkbox/Radio custom icons must render svg to receive…

3777625

… the focus indicator

Navigation Menu

Uh oh!

Uh oh!

[material-ui] Add theme.focusVisible opt-in keyboard focus ring - #48743

[material-ui] Add theme.focusVisible opt-in keyboard focus ring#48743
siriwatknp wants to merge 86 commits into
mui:masterfrom
siriwatknp:focus-ring-v1

siriwatknp commented Jun 30, 2026 •

edited

Loading

Uh oh!

code-infra-dashboard Bot commented Jun 30, 2026 •

edited

Loading

Uh oh!

LukasTy commented Aug 6, 2026

Uh oh!

silviuaavram commented Aug 6, 2026

Uh oh!

Uh oh!

siriwatknp commented Aug 6, 2026 •

edited

Loading

Uh oh!

LukasTy commented Aug 6, 2026

Uh oh!

siriwatknp commented Aug 10, 2026 •

edited

Loading

Still broken

Uh oh!

siriwatknp commented Aug 10, 2026 •

edited

Loading

Uh oh!

LukasTy commented Aug 10, 2026

Uh oh!

siriwatknp commented Aug 11, 2026

Uh oh!

LukasTy commented Aug 11, 2026

Uh oh!

siriwatknp commented Aug 11, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Uh oh!

Conversation

siriwatknp commented Jun 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

For Reviewers

Uh oh!

code-infra-dashboard Bot commented Jun 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploy preview

Bundle size

Uh oh!

LukasTy commented Aug 6, 2026

Uh oh!

silviuaavram commented Aug 6, 2026

Uh oh!

Uh oh!

siriwatknp commented Aug 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Latest changes

Uh oh!

LukasTy commented Aug 6, 2026

Fixed since the last round

Still broken

Follow-ups

Tests

Uh oh!

siriwatknp commented Aug 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Still broken

Uh oh!

siriwatknp commented Aug 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

LukasTy commented Aug 10, 2026

Remaining

Nits

Uh oh!

siriwatknp commented Aug 11, 2026

Uh oh!

LukasTy commented Aug 11, 2026

Uh oh!

siriwatknp commented Aug 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

siriwatknp commented Jun 30, 2026 •

edited

Loading

code-infra-dashboard Bot commented Jun 30, 2026 •

edited

Loading

siriwatknp commented Aug 6, 2026 •

edited

Loading

siriwatknp commented Aug 10, 2026 •

edited

Loading

siriwatknp commented Aug 10, 2026 •

edited

Loading

siriwatknp commented Aug 11, 2026 •

edited

Loading