Custom content type icons loaded via ![]()
tag in ContentIcon can be dark-colored (black or near-black), which makes them invisible or hard to see against dark theme backgrounds. This affects the isUnknownType rendering path where icons provided by content type developers
are displayed as-is. Icons can be SVG or multicolor PNG, so a simple CSS invert() filter is not a viable solution as it would distort colors in multicolor icons.
Currently there is no adaptation for theme when rendering custom content type icons. Built-in content types use Lucide icons which inherit text color and work fine in both themes.
Possible approaches:
- Add a subtle light background container behind custom icons in dark mode, preserving original colors while ensuring visibility
- Introduce dark mode icon variants, allowing content type developers to provide a separate icon for dark theme
Rationale:
Dark theme support should not break visibility of third-party content type icons. Users working in dark mode may not realize icons are present, leading to a degraded browsing experience.
Drafted with AI assistance
Custom content type icons loaded via![]()
tag in ContentIcon can be dark-colored (black or near-black), which makes them invisible or hard to see against dark theme backgrounds. This affects the isUnknownType rendering path where icons provided by content type developers
are displayed as-is. Icons can be SVG or multicolor PNG, so a simple CSS invert() filter is not a viable solution as it would distort colors in multicolor icons.
Currently there is no adaptation for theme when rendering custom content type icons. Built-in content types use Lucide icons which inherit text color and work fine in both themes.
Possible approaches:
Rationale:
Dark theme support should not break visibility of third-party content type icons. Users working in dark mode may not realize icons are present, leading to a degraded browsing experience.
Drafted with AI assistance