fix(mobile): show high usage limit fills - #9742
Open
none23 wants to merge 1 commit into
Open
Conversation
Contributor
ApprovabilityVerdict: Not approved Macroscope's review found this PR not approvable — This change wires warning and destructive colors into existing mobile usage-limit rendering and updates the shipped light/dark and built-in theme defaults. Because it changes product defaults across the mobile theme system, human review is warranted. You can add or adjust custom eligibility rules. Learn more. |
none23
marked this pull request as draft
September 4, 2026 18:18
none23
force-pushed
the
fix/android-usage-bar-fill
branch
from
September 4, 2026 18:25
de4c226 to
eaea60a
Compare
none23
force-pushed
the
fix/android-usage-bar-fill
branch
from
September 4, 2026 18:30
eaea60a to
59d2abe
Compare
none23
force-pushed
the
fix/android-usage-bar-fill
branch
from
September 4, 2026 18:35
59d2abe to
29d7b3f
Compare
none23
marked this pull request as ready for review
September 4, 2026 19:30
macroscopeapp
Bot
dismissed
their stale review
September 4, 2026 19:33
Dismissing prior approval to re-evaluate 29d7b3f
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
Mobile now exposes the shared warning and destructive color roles through its Uniwind theme variables, including generated custom themes.
Why
Usage limit fills already use semantic warning and destructive classes, but mobile did not register those colors. Defining the missing theme variables makes the fills visible while preserving each theme’s palette.
UI Changes
Checklist
Authored with GPT-5.6 Sol via the Codex harness in T3 Code.
Note
Low Risk
Theme-token and generated CSS updates only; no auth, data, or business-logic changes.
Overview
Adds
--color-warningand--color-destructiveto the mobile Uniwind theme so semanticbg-warning/bg-destructiveclasses (e.g. usage limit progress fills) resolve instead of rendering invisible.createMobileThemeVariablesnow maps shared palettewarninganderrorinto those CSS variables; defaultglobal.csslight/dark tokens and regeneratedgenerated-uniwind-*outputs include per-theme values. Tests expect 67 theme variables and assert the new mappings.Reviewed by Cursor Bugbot for commit 29d7b3f. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Add
warninganddestructivecolor variables to mobile themeswarninganddestructivecustom properties to both light and dark mobile theme definitions in global.css, with generated output in the Uniwind theme filescreateMobileThemeVariablesin mobileTheme.ts now mapswarningfrom the native warning color anddestructivefrom the native error color of the selectedThemeColorspaletteMacroscope summarized 29d7b3f.