fix(mobile): pressed and disabled styles no longer apply unconditionally by juliusmarminge · Pull Request #9355 · pingdotgg/t3code

juliusmarminge · 2026-09-03T05:48:54Z

Problem

After #9331 pinned the monorepo to tailwindcss@4.3.3, every active:, disabled:, theme, data-* and rtl: variant on mobile compiled as if it had no condition. The visible symptom (reported in #mobile-ios) was the Appearance screen: each theme card's active:bg-subtle press overlay rendered permanently, so every card was tinted pink on T3 Chat. The same applies to every other active: press state in the app.

Tailwind 4.3.3 stopped nesting variants under the utility class and emits compound selectors instead:

/* <= 4.3.2 *//* 4.3.3 */
.active\:bg-subtle { &:active {…} } .active\:bg-subtle:active {…}

Uniwind 1.11.0 only reads variant tokens from nested rules, so on the flattened form it never sets the active/disabled/theme flag.

Fix

Extend the existing patches/uniwind@1.11.0.patch so the processor also reads variant tokens that follow the leading class token. Compound selectors the runtime cannot express ([aria-disabled="true"]) are dropped instead of treated as unconditional, which matches what the nested form compiled to before. Both the four dist bundles and the TypeScript source in the patch are updated.

Verified by running Uniwind's ProcessorBuilder on both selector shapes and on the real apps/mobile/global.css: active:* entries now carry active: true, disabled:* carry disabled: true, plain utilities are unchanged.

No screenshots: this was fixed on a Linux box without an iOS simulator. The before is in the Discord thread; a TestFlight build off this branch should show the theme cards back to bg-card.

Written by Claude Fable 5 in Claude Code.

🤖 Generated with Claude Code

Note

Medium Risk
Changes vendored Uniwind CSS compilation and native style reinit behavior; incorrect variant parsing could still mis-apply press/theme/disabled styles app-wide on mobile.

Overview
Extends the uniwind@1.11.0 patch so mobile styling works again after Tailwind 4.3.3 started emitting flat compound selectors (e.g. .active\:bg-subtle:active) instead of nested &:active rules. Uniwind’s ProcessorBuilder now pulls active, disabled, focus, theme, RTL, and data-* variant flags from tokens after the utility class via readSelectorVariants / withSelectorVariants, and ignores trailing selector parts the native runtime cannot represent so they are not applied unconditionally.

The Metro transformer also computes a SHA-256 fingerprint of compiled styles plus themes and passes it into Uniwind.__reinit; in __DEV__, native config skips full reinit when the fingerprint is unchanged (avoids redundant work on hot reload). pnpm-lock.yaml updates the patch hash for the enlarged patch.

^{Reviewed by Cursor Bugbot for commit ff068fe. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix pressed and disabled styles applying unconditionally in mobile CSS processor

Patches uniwind@1.11.0 to fix selector-variant parsing so pressed and disabled styles only apply when their conditions match. Updates bundled outputs, Metro transformer sections, and native configuration to stay consistent with the patched parser.

^{Macroscope summarized ff068fe.}

Tailwind 4.3.3 stopped nesting variants under the utility class (`.active\:x { &:active {} }`) and emits compound selectors instead (`.active\:x:active {}`). Uniwind 1.11.0 only reads variant tokens from nested rules, so after #9331 pinned the monorepo to 4.3.3 every `active:`, `disabled:`, theme, data-* and rtl variant on mobile compiled as if it had no condition. The visible symptom was the appearance screen: each theme card's `active:bg-subtle` press overlay rendered permanently. Extend the existing uniwind patch so the processor also reads variant tokens that follow the leading class token, and drop compound selectors it cannot express (`[aria-disabled="true"]`) instead of treating them as unconditional, which matches what the nested form compiled to before. Co-Authored-By: Claude Code <noreply@anthropic.com>

github-actions · 2026-09-03T05:51:10Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.7 KiB	−7 B (−0.0%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−2 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.7 KiB	−5 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	58.5 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	−8 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	−1 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.6 KiB	−7 B (−0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: ff068fe · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-09-03T05:58:51Z

Approvability

Verdict: Approved at ff068fe

Macroscope's review found this PR approvable — This is a focused mobile CSS-processor compatibility fix that restores active, disabled, theme, RTL, and data-attribute conditions while dropping selectors the native runtime cannot represent. The accompanying lockfile change only updates the patch integrity reference, with no product-default or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

juliusmarminge · 2026-09-03T05:48:54Z

Problem

After #9331 pinned the monorepo to tailwindcss@4.3.3, every active:, disabled:, theme, data-* and rtl: variant on mobile compiled as if it had no condition. The visible symptom (reported in #mobile-ios) was the Appearance screen: each theme card's active:bg-subtle press overlay rendered permanently, so every card was tinted pink on T3 Chat. The same applies to every other active: press state in the app.

Tailwind 4.3.3 stopped nesting variants under the utility class and emits compound selectors instead:

/* <= 4.3.2 *//* 4.3.3 */
.active\:bg-subtle { &:active {…} } .active\:bg-subtle:active {…}

Uniwind 1.11.0 only reads variant tokens from nested rules, so on the flattened form it never sets the active/disabled/theme flag.

Fix

Extend the existing patches/uniwind@1.11.0.patch so the processor also reads variant tokens that follow the leading class token. Compound selectors the runtime cannot express ([aria-disabled="true"]) are dropped instead of treated as unconditional, which matches what the nested form compiled to before. Both the four dist bundles and the TypeScript source in the patch are updated.

Verified by running Uniwind's ProcessorBuilder on both selector shapes and on the real apps/mobile/global.css: active:* entries now carry active: true, disabled:* carry disabled: true, plain utilities are unchanged.

No screenshots: this was fixed on a Linux box without an iOS simulator. The before is in the Discord thread; a TestFlight build off this branch should show the theme cards back to bg-card.

Written by Claude Fable 5 in Claude Code.

🤖 Generated with Claude Code

Note

Medium Risk
Changes vendored Uniwind CSS compilation and native style reinit behavior; incorrect variant parsing could still mis-apply press/theme/disabled styles app-wide on mobile.

Overview
Extends the uniwind@1.11.0 patch so mobile styling works again after Tailwind 4.3.3 started emitting flat compound selectors (e.g. .active\:bg-subtle:active) instead of nested &:active rules. Uniwind’s ProcessorBuilder now pulls active, disabled, focus, theme, RTL, and data-* variant flags from tokens after the utility class via readSelectorVariants / withSelectorVariants, and ignores trailing selector parts the native runtime cannot represent so they are not applied unconditionally.

The Metro transformer also computes a SHA-256 fingerprint of compiled styles plus themes and passes it into Uniwind.__reinit; in __DEV__, native config skips full reinit when the fingerprint is unchanged (avoids redundant work on hot reload). pnpm-lock.yaml updates the patch hash for the enlarged patch.

^{Reviewed by Cursor Bugbot for commit ff068fe. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix pressed and disabled styles applying unconditionally in mobile CSS processor

Patches uniwind@1.11.0 to fix selector-variant parsing so pressed and disabled styles only apply when their conditions match. Updates bundled outputs, Metro transformer sections, and native configuration to stay consistent with the patched parser.

^{Macroscope summarized ff068fe.}

Tailwind 4.3.3 stopped nesting variants under the utility class (`.active\:x { &:active {} }`) and emits compound selectors instead (`.active\:x:active {}`). Uniwind 1.11.0 only reads variant tokens from nested rules, so after #9331 pinned the monorepo to 4.3.3 every `active:`, `disabled:`, theme, data-* and rtl variant on mobile compiled as if it had no condition. The visible symptom was the appearance screen: each theme card's `active:bg-subtle` press overlay rendered permanently. Extend the existing uniwind patch so the processor also reads variant tokens that follow the leading class token, and drop compound selectors it cannot express (`[aria-disabled="true"]`) instead of treating them as unconditional, which matches what the nested form compiled to before. Co-Authored-By: Claude Code <noreply@anthropic.com>

github-actions · 2026-09-03T05:51:10Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.7 KiB	−7 B (−0.0%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−2 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.7 KiB	−5 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	58.5 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	−8 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	−1 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.6 KiB	−7 B (−0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: ff068fe · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-09-03T05:58:51Z

Approvability

Verdict: Approved at ff068fe

Macroscope's review found this PR approvable — This is a focused mobile CSS-processor compatibility fix that restores active, disabled, theme, RTL, and data-attribute conditions while dropping selectors the native runtime cannot represent. The accompanying lockfile change only updates the patch integrity reference, with no product-default or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

juliusmarminge · 2026-09-03T05:48:54Z

Problem

After #9331 pinned the monorepo to tailwindcss@4.3.3, every active:, disabled:, theme, data-* and rtl: variant on mobile compiled as if it had no condition. The visible symptom (reported in #mobile-ios) was the Appearance screen: each theme card's active:bg-subtle press overlay rendered permanently, so every card was tinted pink on T3 Chat. The same applies to every other active: press state in the app.

Tailwind 4.3.3 stopped nesting variants under the utility class and emits compound selectors instead:

/* <= 4.3.2 *//* 4.3.3 */
.active\:bg-subtle { &:active {…} } .active\:bg-subtle:active {…}

Uniwind 1.11.0 only reads variant tokens from nested rules, so on the flattened form it never sets the active/disabled/theme flag.

Fix

Extend the existing patches/uniwind@1.11.0.patch so the processor also reads variant tokens that follow the leading class token. Compound selectors the runtime cannot express ([aria-disabled="true"]) are dropped instead of treated as unconditional, which matches what the nested form compiled to before. Both the four dist bundles and the TypeScript source in the patch are updated.

Verified by running Uniwind's ProcessorBuilder on both selector shapes and on the real apps/mobile/global.css: active:* entries now carry active: true, disabled:* carry disabled: true, plain utilities are unchanged.

No screenshots: this was fixed on a Linux box without an iOS simulator. The before is in the Discord thread; a TestFlight build off this branch should show the theme cards back to bg-card.

Written by Claude Fable 5 in Claude Code.

🤖 Generated with Claude Code

Note

Medium Risk
Changes vendored Uniwind CSS compilation and native style reinit behavior; incorrect variant parsing could still mis-apply press/theme/disabled styles app-wide on mobile.

Overview
Extends the uniwind@1.11.0 patch so mobile styling works again after Tailwind 4.3.3 started emitting flat compound selectors (e.g. .active\:bg-subtle:active) instead of nested &:active rules. Uniwind’s ProcessorBuilder now pulls active, disabled, focus, theme, RTL, and data-* variant flags from tokens after the utility class via readSelectorVariants / withSelectorVariants, and ignores trailing selector parts the native runtime cannot represent so they are not applied unconditionally.

The Metro transformer also computes a SHA-256 fingerprint of compiled styles plus themes and passes it into Uniwind.__reinit; in __DEV__, native config skips full reinit when the fingerprint is unchanged (avoids redundant work on hot reload). pnpm-lock.yaml updates the patch hash for the enlarged patch.

^{Reviewed by Cursor Bugbot for commit ff068fe. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix pressed and disabled styles applying unconditionally in mobile CSS processor

Patches uniwind@1.11.0 to fix selector-variant parsing so pressed and disabled styles only apply when their conditions match. Updates bundled outputs, Metro transformer sections, and native configuration to stay consistent with the patched parser.

^{Macroscope summarized ff068fe.}

Tailwind 4.3.3 stopped nesting variants under the utility class (`.active\:x { &:active {} }`) and emits compound selectors instead (`.active\:x:active {}`). Uniwind 1.11.0 only reads variant tokens from nested rules, so after #9331 pinned the monorepo to 4.3.3 every `active:`, `disabled:`, theme, data-* and rtl variant on mobile compiled as if it had no condition. The visible symptom was the appearance screen: each theme card's `active:bg-subtle` press overlay rendered permanently. Extend the existing uniwind patch so the processor also reads variant tokens that follow the leading class token, and drop compound selectors it cannot express (`[aria-disabled="true"]`) instead of treating them as unconditional, which matches what the nested form compiled to before. Co-Authored-By: Claude Code <noreply@anthropic.com>

github-actions · 2026-09-03T05:51:10Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.7 KiB	−7 B (−0.0%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−2 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.7 KiB	−5 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	58.5 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	−8 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	−1 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.6 KiB	−7 B (−0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: ff068fe · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-09-03T05:58:51Z

Approvability

Verdict: Approved at ff068fe

Macroscope's review found this PR approvable — This is a focused mobile CSS-processor compatibility fix that restores active, disabled, theme, RTL, and data-attribute conditions while dropping selectors the native runtime cannot represent. The accompanying lockfile change only updates the patch integrity reference, with no product-default or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

juliusmarminge · 2026-09-03T05:48:54Z

Problem

After #9331 pinned the monorepo to tailwindcss@4.3.3, every active:, disabled:, theme, data-* and rtl: variant on mobile compiled as if it had no condition. The visible symptom (reported in #mobile-ios) was the Appearance screen: each theme card's active:bg-subtle press overlay rendered permanently, so every card was tinted pink on T3 Chat. The same applies to every other active: press state in the app.

Tailwind 4.3.3 stopped nesting variants under the utility class and emits compound selectors instead:

/* <= 4.3.2 *//* 4.3.3 */
.active\:bg-subtle { &:active {…} } .active\:bg-subtle:active {…}

Uniwind 1.11.0 only reads variant tokens from nested rules, so on the flattened form it never sets the active/disabled/theme flag.

Fix

Extend the existing patches/uniwind@1.11.0.patch so the processor also reads variant tokens that follow the leading class token. Compound selectors the runtime cannot express ([aria-disabled="true"]) are dropped instead of treated as unconditional, which matches what the nested form compiled to before. Both the four dist bundles and the TypeScript source in the patch are updated.

Verified by running Uniwind's ProcessorBuilder on both selector shapes and on the real apps/mobile/global.css: active:* entries now carry active: true, disabled:* carry disabled: true, plain utilities are unchanged.

No screenshots: this was fixed on a Linux box without an iOS simulator. The before is in the Discord thread; a TestFlight build off this branch should show the theme cards back to bg-card.

Written by Claude Fable 5 in Claude Code.

🤖 Generated with Claude Code

Note

Medium Risk
Changes vendored Uniwind CSS compilation and native style reinit behavior; incorrect variant parsing could still mis-apply press/theme/disabled styles app-wide on mobile.

Overview
Extends the uniwind@1.11.0 patch so mobile styling works again after Tailwind 4.3.3 started emitting flat compound selectors (e.g. .active\:bg-subtle:active) instead of nested &:active rules. Uniwind’s ProcessorBuilder now pulls active, disabled, focus, theme, RTL, and data-* variant flags from tokens after the utility class via readSelectorVariants / withSelectorVariants, and ignores trailing selector parts the native runtime cannot represent so they are not applied unconditionally.

The Metro transformer also computes a SHA-256 fingerprint of compiled styles plus themes and passes it into Uniwind.__reinit; in __DEV__, native config skips full reinit when the fingerprint is unchanged (avoids redundant work on hot reload). pnpm-lock.yaml updates the patch hash for the enlarged patch.

^{Reviewed by Cursor Bugbot for commit ff068fe. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix pressed and disabled styles applying unconditionally in mobile CSS processor

Patches uniwind@1.11.0 to fix selector-variant parsing so pressed and disabled styles only apply when their conditions match. Updates bundled outputs, Metro transformer sections, and native configuration to stay consistent with the patched parser.

^{Macroscope summarized ff068fe.}

Tailwind 4.3.3 stopped nesting variants under the utility class (`.active\:x { &:active {} }`) and emits compound selectors instead (`.active\:x:active {}`). Uniwind 1.11.0 only reads variant tokens from nested rules, so after #9331 pinned the monorepo to 4.3.3 every `active:`, `disabled:`, theme, data-* and rtl variant on mobile compiled as if it had no condition. The visible symptom was the appearance screen: each theme card's `active:bg-subtle` press overlay rendered permanently. Extend the existing uniwind patch so the processor also reads variant tokens that follow the leading class token, and drop compound selectors it cannot express (`[aria-disabled="true"]`) instead of treating them as unconditional, which matches what the nested form compiled to before. Co-Authored-By: Claude Code <noreply@anthropic.com>

github-actions · 2026-09-03T05:51:10Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.7 KiB	−7 B (−0.0%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−2 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.7 KiB	−5 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	58.5 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	−8 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	−1 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.6 KiB	−7 B (−0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: ff068fe · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-09-03T05:58:51Z

Approvability

Verdict: Approved at ff068fe

Macroscope's review found this PR approvable — This is a focused mobile CSS-processor compatibility fix that restores active, disabled, theme, RTL, and data-attribute conditions while dropping selectors the native runtime cannot represent. The accompanying lockfile change only updates the patch integrity reference, with no product-default or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

juliusmarminge · 2026-09-03T05:48:54Z

Problem

After #9331 pinned the monorepo to tailwindcss@4.3.3, every active:, disabled:, theme, data-* and rtl: variant on mobile compiled as if it had no condition. The visible symptom (reported in #mobile-ios) was the Appearance screen: each theme card's active:bg-subtle press overlay rendered permanently, so every card was tinted pink on T3 Chat. The same applies to every other active: press state in the app.

Tailwind 4.3.3 stopped nesting variants under the utility class and emits compound selectors instead:

/* <= 4.3.2 *//* 4.3.3 */
.active\:bg-subtle { &:active {…} } .active\:bg-subtle:active {…}

Uniwind 1.11.0 only reads variant tokens from nested rules, so on the flattened form it never sets the active/disabled/theme flag.

Fix

Extend the existing patches/uniwind@1.11.0.patch so the processor also reads variant tokens that follow the leading class token. Compound selectors the runtime cannot express ([aria-disabled="true"]) are dropped instead of treated as unconditional, which matches what the nested form compiled to before. Both the four dist bundles and the TypeScript source in the patch are updated.

Verified by running Uniwind's ProcessorBuilder on both selector shapes and on the real apps/mobile/global.css: active:* entries now carry active: true, disabled:* carry disabled: true, plain utilities are unchanged.

No screenshots: this was fixed on a Linux box without an iOS simulator. The before is in the Discord thread; a TestFlight build off this branch should show the theme cards back to bg-card.

Written by Claude Fable 5 in Claude Code.

🤖 Generated with Claude Code

Note

Medium Risk
Changes vendored Uniwind CSS compilation and native style reinit behavior; incorrect variant parsing could still mis-apply press/theme/disabled styles app-wide on mobile.

Overview
Extends the uniwind@1.11.0 patch so mobile styling works again after Tailwind 4.3.3 started emitting flat compound selectors (e.g. .active\:bg-subtle:active) instead of nested &:active rules. Uniwind’s ProcessorBuilder now pulls active, disabled, focus, theme, RTL, and data-* variant flags from tokens after the utility class via readSelectorVariants / withSelectorVariants, and ignores trailing selector parts the native runtime cannot represent so they are not applied unconditionally.

The Metro transformer also computes a SHA-256 fingerprint of compiled styles plus themes and passes it into Uniwind.__reinit; in __DEV__, native config skips full reinit when the fingerprint is unchanged (avoids redundant work on hot reload). pnpm-lock.yaml updates the patch hash for the enlarged patch.

^{Reviewed by Cursor Bugbot for commit ff068fe. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix pressed and disabled styles applying unconditionally in mobile CSS processor

Patches uniwind@1.11.0 to fix selector-variant parsing so pressed and disabled styles only apply when their conditions match. Updates bundled outputs, Metro transformer sections, and native configuration to stay consistent with the patched parser.

^{Macroscope summarized ff068fe.}

Tailwind 4.3.3 stopped nesting variants under the utility class (`.active\:x { &:active {} }`) and emits compound selectors instead (`.active\:x:active {}`). Uniwind 1.11.0 only reads variant tokens from nested rules, so after #9331 pinned the monorepo to 4.3.3 every `active:`, `disabled:`, theme, data-* and rtl variant on mobile compiled as if it had no condition. The visible symptom was the appearance screen: each theme card's `active:bg-subtle` press overlay rendered permanently. Extend the existing uniwind patch so the processor also reads variant tokens that follow the leading class token, and drop compound selectors it cannot express (`[aria-disabled="true"]`) instead of treating them as unconditional, which matches what the nested form compiled to before. Co-Authored-By: Claude Code <noreply@anthropic.com>

github-actions · 2026-09-03T05:51:10Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.7 KiB	−7 B (−0.0%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−2 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.7 KiB	−5 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	58.5 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	−8 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	−1 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.6 KiB	−7 B (−0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: ff068fe · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-09-03T05:58:51Z

Approvability

Verdict: Approved at ff068fe

Macroscope's review found this PR approvable — This is a focused mobile CSS-processor compatibility fix that restores active, disabled, theme, RTL, and data-attribute conditions while dropping selectors the native runtime cannot represent. The accompanying lockfile change only updates the patch integrity reference, with no product-default or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

juliusmarminge · 2026-09-03T05:48:54Z

Problem

After #9331 pinned the monorepo to tailwindcss@4.3.3, every active:, disabled:, theme, data-* and rtl: variant on mobile compiled as if it had no condition. The visible symptom (reported in #mobile-ios) was the Appearance screen: each theme card's active:bg-subtle press overlay rendered permanently, so every card was tinted pink on T3 Chat. The same applies to every other active: press state in the app.

Tailwind 4.3.3 stopped nesting variants under the utility class and emits compound selectors instead:

/* <= 4.3.2 *//* 4.3.3 */
.active\:bg-subtle { &:active {…} } .active\:bg-subtle:active {…}

Uniwind 1.11.0 only reads variant tokens from nested rules, so on the flattened form it never sets the active/disabled/theme flag.

Fix

Extend the existing patches/uniwind@1.11.0.patch so the processor also reads variant tokens that follow the leading class token. Compound selectors the runtime cannot express ([aria-disabled="true"]) are dropped instead of treated as unconditional, which matches what the nested form compiled to before. Both the four dist bundles and the TypeScript source in the patch are updated.

Verified by running Uniwind's ProcessorBuilder on both selector shapes and on the real apps/mobile/global.css: active:* entries now carry active: true, disabled:* carry disabled: true, plain utilities are unchanged.

No screenshots: this was fixed on a Linux box without an iOS simulator. The before is in the Discord thread; a TestFlight build off this branch should show the theme cards back to bg-card.

Written by Claude Fable 5 in Claude Code.

🤖 Generated with Claude Code

Note

Medium Risk
Changes vendored Uniwind CSS compilation and native style reinit behavior; incorrect variant parsing could still mis-apply press/theme/disabled styles app-wide on mobile.

Overview
Extends the uniwind@1.11.0 patch so mobile styling works again after Tailwind 4.3.3 started emitting flat compound selectors (e.g. .active\:bg-subtle:active) instead of nested &:active rules. Uniwind’s ProcessorBuilder now pulls active, disabled, focus, theme, RTL, and data-* variant flags from tokens after the utility class via readSelectorVariants / withSelectorVariants, and ignores trailing selector parts the native runtime cannot represent so they are not applied unconditionally.

The Metro transformer also computes a SHA-256 fingerprint of compiled styles plus themes and passes it into Uniwind.__reinit; in __DEV__, native config skips full reinit when the fingerprint is unchanged (avoids redundant work on hot reload). pnpm-lock.yaml updates the patch hash for the enlarged patch.

^{Reviewed by Cursor Bugbot for commit ff068fe. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix pressed and disabled styles applying unconditionally in mobile CSS processor

Patches uniwind@1.11.0 to fix selector-variant parsing so pressed and disabled styles only apply when their conditions match. Updates bundled outputs, Metro transformer sections, and native configuration to stay consistent with the patched parser.

^{Macroscope summarized ff068fe.}

Tailwind 4.3.3 stopped nesting variants under the utility class (`.active\:x { &:active {} }`) and emits compound selectors instead (`.active\:x:active {}`). Uniwind 1.11.0 only reads variant tokens from nested rules, so after #9331 pinned the monorepo to 4.3.3 every `active:`, `disabled:`, theme, data-* and rtl variant on mobile compiled as if it had no condition. The visible symptom was the appearance screen: each theme card's `active:bg-subtle` press overlay rendered permanently. Extend the existing uniwind patch so the processor also reads variant tokens that follow the leading class token, and drop compound selectors it cannot express (`[aria-disabled="true"]`) instead of treating them as unconditional, which matches what the nested form compiled to before. Co-Authored-By: Claude Code <noreply@anthropic.com>

github-actions · 2026-09-03T05:51:10Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.7 KiB	−7 B (−0.0%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−2 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.7 KiB	−5 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	58.5 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	−8 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	−1 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.6 KiB	−7 B (−0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: ff068fe · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-09-03T05:58:51Z

Approvability

Verdict: Approved at ff068fe

Macroscope's review found this PR approvable — This is a focused mobile CSS-processor compatibility fix that restores active, disabled, theme, RTL, and data-attribute conditions while dropping selectors the native runtime cannot represent. The accompanying lockfile change only updates the patch integrity reference, with no product-default or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

juliusmarminge · 2026-09-03T05:48:54Z

Problem

After #9331 pinned the monorepo to tailwindcss@4.3.3, every active:, disabled:, theme, data-* and rtl: variant on mobile compiled as if it had no condition. The visible symptom (reported in #mobile-ios) was the Appearance screen: each theme card's active:bg-subtle press overlay rendered permanently, so every card was tinted pink on T3 Chat. The same applies to every other active: press state in the app.

Tailwind 4.3.3 stopped nesting variants under the utility class and emits compound selectors instead:

/* <= 4.3.2 *//* 4.3.3 */
.active\:bg-subtle { &:active {…} } .active\:bg-subtle:active {…}

Uniwind 1.11.0 only reads variant tokens from nested rules, so on the flattened form it never sets the active/disabled/theme flag.

Fix

Extend the existing patches/uniwind@1.11.0.patch so the processor also reads variant tokens that follow the leading class token. Compound selectors the runtime cannot express ([aria-disabled="true"]) are dropped instead of treated as unconditional, which matches what the nested form compiled to before. Both the four dist bundles and the TypeScript source in the patch are updated.

Verified by running Uniwind's ProcessorBuilder on both selector shapes and on the real apps/mobile/global.css: active:* entries now carry active: true, disabled:* carry disabled: true, plain utilities are unchanged.

No screenshots: this was fixed on a Linux box without an iOS simulator. The before is in the Discord thread; a TestFlight build off this branch should show the theme cards back to bg-card.

Written by Claude Fable 5 in Claude Code.

🤖 Generated with Claude Code

Note

Medium Risk
Changes vendored Uniwind CSS compilation and native style reinit behavior; incorrect variant parsing could still mis-apply press/theme/disabled styles app-wide on mobile.

Overview
Extends the uniwind@1.11.0 patch so mobile styling works again after Tailwind 4.3.3 started emitting flat compound selectors (e.g. .active\:bg-subtle:active) instead of nested &:active rules. Uniwind’s ProcessorBuilder now pulls active, disabled, focus, theme, RTL, and data-* variant flags from tokens after the utility class via readSelectorVariants / withSelectorVariants, and ignores trailing selector parts the native runtime cannot represent so they are not applied unconditionally.

The Metro transformer also computes a SHA-256 fingerprint of compiled styles plus themes and passes it into Uniwind.__reinit; in __DEV__, native config skips full reinit when the fingerprint is unchanged (avoids redundant work on hot reload). pnpm-lock.yaml updates the patch hash for the enlarged patch.

^{Reviewed by Cursor Bugbot for commit ff068fe. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix pressed and disabled styles applying unconditionally in mobile CSS processor

Patches uniwind@1.11.0 to fix selector-variant parsing so pressed and disabled styles only apply when their conditions match. Updates bundled outputs, Metro transformer sections, and native configuration to stay consistent with the patched parser.

^{Macroscope summarized ff068fe.}

Tailwind 4.3.3 stopped nesting variants under the utility class (`.active\:x { &:active {} }`) and emits compound selectors instead (`.active\:x:active {}`). Uniwind 1.11.0 only reads variant tokens from nested rules, so after #9331 pinned the monorepo to 4.3.3 every `active:`, `disabled:`, theme, data-* and rtl variant on mobile compiled as if it had no condition. The visible symptom was the appearance screen: each theme card's `active:bg-subtle` press overlay rendered permanently. Extend the existing uniwind patch so the processor also reads variant tokens that follow the leading class token, and drop compound selectors it cannot express (`[aria-disabled="true"]`) instead of treating them as unconditional, which matches what the nested form compiled to before. Co-Authored-By: Claude Code <noreply@anthropic.com>

github-actions · 2026-09-03T05:51:10Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.7 KiB	−7 B (−0.0%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−2 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.7 KiB	−5 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	58.5 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	−8 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	−1 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.6 KiB	−7 B (−0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: ff068fe · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-09-03T05:58:51Z

Approvability

Verdict: Approved at ff068fe

Macroscope's review found this PR approvable — This is a focused mobile CSS-processor compatibility fix that restores active, disabled, theme, RTL, and data-attribute conditions while dropping selectors the native runtime cannot represent. The accompanying lockfile change only updates the patch integrity reference, with no product-default or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

juliusmarminge · 2026-09-03T05:48:54Z

Problem

After #9331 pinned the monorepo to tailwindcss@4.3.3, every active:, disabled:, theme, data-* and rtl: variant on mobile compiled as if it had no condition. The visible symptom (reported in #mobile-ios) was the Appearance screen: each theme card's active:bg-subtle press overlay rendered permanently, so every card was tinted pink on T3 Chat. The same applies to every other active: press state in the app.

Tailwind 4.3.3 stopped nesting variants under the utility class and emits compound selectors instead:

/* <= 4.3.2 *//* 4.3.3 */
.active\:bg-subtle { &:active {…} } .active\:bg-subtle:active {…}

Uniwind 1.11.0 only reads variant tokens from nested rules, so on the flattened form it never sets the active/disabled/theme flag.

Fix

Extend the existing patches/uniwind@1.11.0.patch so the processor also reads variant tokens that follow the leading class token. Compound selectors the runtime cannot express ([aria-disabled="true"]) are dropped instead of treated as unconditional, which matches what the nested form compiled to before. Both the four dist bundles and the TypeScript source in the patch are updated.

Verified by running Uniwind's ProcessorBuilder on both selector shapes and on the real apps/mobile/global.css: active:* entries now carry active: true, disabled:* carry disabled: true, plain utilities are unchanged.

No screenshots: this was fixed on a Linux box without an iOS simulator. The before is in the Discord thread; a TestFlight build off this branch should show the theme cards back to bg-card.

Written by Claude Fable 5 in Claude Code.

🤖 Generated with Claude Code

Note

Medium Risk
Changes vendored Uniwind CSS compilation and native style reinit behavior; incorrect variant parsing could still mis-apply press/theme/disabled styles app-wide on mobile.

Overview
Extends the uniwind@1.11.0 patch so mobile styling works again after Tailwind 4.3.3 started emitting flat compound selectors (e.g. .active\:bg-subtle:active) instead of nested &:active rules. Uniwind’s ProcessorBuilder now pulls active, disabled, focus, theme, RTL, and data-* variant flags from tokens after the utility class via readSelectorVariants / withSelectorVariants, and ignores trailing selector parts the native runtime cannot represent so they are not applied unconditionally.

The Metro transformer also computes a SHA-256 fingerprint of compiled styles plus themes and passes it into Uniwind.__reinit; in __DEV__, native config skips full reinit when the fingerprint is unchanged (avoids redundant work on hot reload). pnpm-lock.yaml updates the patch hash for the enlarged patch.

^{Reviewed by Cursor Bugbot for commit ff068fe. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Fix pressed and disabled styles applying unconditionally in mobile CSS processor

Patches uniwind@1.11.0 to fix selector-variant parsing so pressed and disabled styles only apply when their conditions match. Updates bundled outputs, Metro transformer sections, and native configuration to stay consistent with the patched parser.

^{Macroscope summarized ff068fe.}

Tailwind 4.3.3 stopped nesting variants under the utility class (`.active\:x { &:active {} }`) and emits compound selectors instead (`.active\:x:active {}`). Uniwind 1.11.0 only reads variant tokens from nested rules, so after #9331 pinned the monorepo to 4.3.3 every `active:`, `disabled:`, theme, data-* and rtl variant on mobile compiled as if it had no condition. The visible symptom was the appearance screen: each theme card's `active:bg-subtle` press overlay rendered permanently. Extend the existing uniwind patch so the processor also reads variant tokens that follow the leading class token, and drop compound selectors it cannot express (`[aria-disabled="true"]`) instead of treating them as unconditional, which matches what the nested form compiled to before. Co-Authored-By: Claude Code <noreply@anthropic.com>

github-actions · 2026-09-03T05:51:10Z

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.8 KiB	13.7 KiB	−7 B (−0.0%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.0 KiB	−2 B (−0.0%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.7 KiB	6.7 KiB	−5 B (−0.1%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	58.5 KiB	58.5 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.6 KiB	13.6 KiB	−8 B (−0.1%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.0 KiB	7.0 KiB	−1 B (−0.0%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.6 KiB	6.6 KiB	−7 B (−0.1%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.9 KiB	57.9 KiB	0 B (0.0%)	66.4 KiB	✅
Claude	Live turn messages	10	10	0 (0.0%)	21	✅

Baseline: 854541a · PR result: ff068fe · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

Codex decoded thread snapshot: 113.8 KiB
Claude decoded thread snapshot: 114.5 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

macroscopeapp · 2026-09-03T05:58:51Z

Approvability

Verdict: Approved at ff068fe

Macroscope's review found this PR approvable — This is a focused mobile CSS-processor compatibility fix that restores active, disabled, theme, RTL, and data-attribute conditions while dropping selectors the native runtime cannot represent. The accompanying lockfile change only updates the patch integrity reference, with no product-default or static-analysis configuration changes.

^{You can add or adjust custom eligibility rules. Learn more.}

github-actionsBot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:XL 500-999 changed lines (additions + deletions). labels Sep 3, 2026

macroscopeappBot approved these changes Sep 3, 2026
View reviewed changes

juliusmarminge merged commit 1f7a3c1 into mainSep 3, 2026
21 checks passed

juliusmarminge deleted the fix/mobile-uniwind-pseudo-variants branch September 3, 2026 06:41

Brentlok mentioned this pull request Sep 3, 2026
Tailwind 4.3.3+ nested variants are not working uni-stack/uniwind#661
Open

juliusmarminge mentioned this pull request Sep 3, 2026
fix: read variant tokens from flattened class selectors uni-stack/uniwind#662
Open

berghtho mentioned this pull request Sep 3, 2026
chore(upstream): sync 2026-09-03 berghtho/t3code#23
Merged