feat: add issue 528 settings and UI rendering fixes - #31
Merged
Conversation
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.
What changed
Why
Issue #528 configuration fields were only available through manual configuration. Separately, suspended virtualized content could return blank after page navigation, and disabling motion wrappers incorrectly prevented configuration cards and loading indicators from rendering normally in low-performance mode.
Validation
bunx tsc --noEmitbun test tests/frontend— 12 passingbun run i18n:check— 539 keys across 7 localesbun run build:tauribun run build:tauri:androidcargo test --workspace— 125 passing