You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a custom theme with editor.colors.addition / editor.colors.deletion / editor.colors.modified configured, the diff pane (v2 WorkspaceDiff) ignores these theme values and uses hardcoded Tailwind CSS variables instead.
Root Cause
In WorkspaceDiff.tsx (lines ~70-86), gitDecorationColors hardcodes Tailwind CSS variables:
This overwrites baseThemeVars which correctly derives from getEditorTheme(theme) → getDiffViewerStyle(), making the theme's editor.colors settings ineffective for the diff view.
Expected Behavior
Diff colors should respect the custom theme's editor.colors.addition, editor.colors.deletion, and editor.colors.modified values. The getDiffViewerStyle() already correctly reads from the theme — removing the hardcoded override in WorkspaceDiff.tsx should fix this.
Steps to Reproduce
Create a custom theme JSON with editor.colors section including addition, deletion, modified
Import and activate the theme in Settings → Appearance
Open the Changes tab to view a diff
Observe that diff colors remain the default Tailwind green/red/yellow regardless of theme settings
Environment
Superset Desktop (macOS)
Custom theme with both terminal and editor sections defined
Closing as a duplicate of #5608, the consolidated tracker for stale themes-appearance issues from the July 2026 stale-issue sweep (no activity since 2026-06-01). If this still applies on a current build, comment on #5608 and we'll reopen.
Activity
Kitenite commentedon Jul 11, 2026
Closing as a duplicate of #5608, the consolidated tracker for stale
themes-appearanceissues from the July 2026 stale-issue sweep (no activity since 2026-06-01). If this still applies on a current build, comment on #5608 and we'll reopen.