dosubot[bot] commented on issue #34503:
URL: https://github.com/apache/superset/issues/34503#issuecomment-3144008719

   <!-- Greeting -->
   Hi @PhilippGrashoff! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping 
the superset team.
   
   <!-- Answer -->
   This is a known limitation in Superset 4.1.x: THEME_OVERRIDES does not 
guarantee a full override of the primary color everywhere in the UI. Some 
components still use hardcoded color values or reference the default theme 
directly, so your custom primary color may not be picked up in all places. This 
is due to a mix of legacy code, incomplete adoption of theme tokens, and the 
evolving theming system. Full coverage is expected to improve in later 
versions, but in 4.1.x, some UI elements will still show the original blue even 
after setting THEME_OVERRIDES [see 
discussion](https://github.com/apache/superset/issues/32847) and [theming 
roadmap](https://github.com/apache/superset/discussions/34397).
   
   There’s no simple switch to force a complete override in 4.1.x. You can try 
targeted CSS overrides for specific elements, but due to CSS specificity and 
dynamic style injection, this may require some trial and error. The theme 
editor (if enabled) or setting THEME_DARK in your config may help tweak some 
tokens, but full coverage is not guaranteed 
[details](https://github.com/apache/superset/issues/34214).
   
   If you need 100% color consistency, it may require waiting for a newer 
release or patching specific frontend components to reference the theme tokens 
everywhere.
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/685682dd-c0d2-4d48-bbe6-3119e7323af2?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/685682dd-c0d2-4d48-bbe6-3119e7323af2?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/685682dd-c0d2-4d48-bbe6-3119e7323af2?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/685682dd-c0d2-4d48-bbe6-3119e7323af2?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/685682dd-c0d2-4d48-bbe6-3119e7323af2?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/685682dd-c0d2-4d48-bbe6-3119e7323af2?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/685682dd-c0d2-4d48-bbe6-3119e7323af2?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat
 with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu
 b)&nbsp;[![Join 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/34503)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to