a11y(settings): fix #660 by guarding the theme section with a retry boundary#791
Merged
mikewheeleer merged 4 commits intoJul 26, 2026
Conversation
|
@TochukwuJustice Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
closes #660
Summary
This change fixes issue #660 by wrapping the theme section in a localized error boundary so a render failure in the theme control no longer blanks the entire settings panel. Before this work, an unexpected crash in theme could take down the surrounding UI. Now, the theme section fails closed, shows an accessible inline fallback, and offers a retry action so the user can attempt to recover without leaving the panel.
The behavior now works like this:
ThemeErrorBoundary.reportErrorseam.This matters because the panel stays usable even when theme rendering is broken, and the failure is surfaced through the existing error-reporting path instead of being swallowed silently. The scope now matches the issue more precisely: only the theme section is isolated.
Full test output from verification: