Skip to content

fix: 152 SVG ICONS that might have color confusion when used on the same component #2608 - #2633

Open
Yue-plus wants to merge 12 commits into
devicons:developfrom
Yue-plus:fix/color-confusion
Open

Yue-plus wants to merge 12 commits into
devicons:developfrom
Yue-plus:fix/color-confusion

Conversation

@Yue-plus

@Yue-plus Yue-plus commented Jan 18, 2026 •

Copy link
Copy Markdown

Fixed 152 SVG ICONS that might have color confusion when used on the same component

Related issues and PR:

- Updated angular-original-wordmark.svg to use simplified IDs and removed unnecessary attributes.
- Cleaned up the structure of angular-original.svg for consistency and readability.
@Yue-plus Yue-plus mentioned this pull request Jan 18, 2026
@Yue-plus

Copy link
Copy Markdown
Author

We need to find a way to automatically check this issue through the workflow. There are another 29 ICONS on the develop branch that have color confusion problems. 😂😂😂

image

@Yue-plus Yue-plus changed the title fix: 123 SVG ICONS that might have color confusion when used on the same component #2608 fix: 152 SVG ICONS that might have color confusion when used on the same component #2608 Jan 18, 2026
Snailedlt and others added 3 commits October 27, 2026 17:40
- Prefix the ids in the 17 SVGs that still had unprefixed ones (some were
  added to develop after this PR started), with the same function the
  build will use.
- jekyll-original-wordmark: re-prefixed from develop's file; the earlier
  rename left <use xlink:href="#l"/"#E"> pointing at ids that no
  longer existed. Also drop a <use> of #j, which never existed.
- vim-original: drop a meaningless xlink:href on a <path>.

Every changed SVG renders pixel-identical to develop.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Snailedlt

Copy link
Copy Markdown
Collaborator

Prepared by Claude (an AI assistant) on behalf of @Snailedlt.

Thanks for this, @Yue-plus! To get it over the line I pushed two commits to your branch:

  • Merged the latest develop, so the icons added since (and the CI fixes) are included.
  • Prefixed the ids in the 17 SVGs that still had unprefixed ones, and repaired jekyll-original-wordmark.svg: its <use xlink:href="#l"> / #E still pointed at the old ids after the rename. Also removed a dangling xlink:href in vim-original.svg.

Every SVG I touched renders pixel-identical to develop, and no SVG in the repo has unprefixed ids or broken references any more.

Next, once the trunk-based migration lands, we'd like to add the automation to this PR too: the check-bot notes unprefixed ids, and the build prefixes them after merge, so this doesn't creep back in.

@Snailedlt
Snailedlt requested review from a team, Snailedlt, Yashh56, canaleal, lunatic-fox and weh and removed request for a team October 28, 2026 13:00
@Snailedlt

Copy link
Copy Markdown
Collaborator

Claude (AI assistant), on behalf of @Snailedlt: Re-checked with the latest develop: all 2137 SVGs have prefixed ids, nothing new to fix. The automation (check-bot warning + prefixing on merge) will be added after the trunk-based migration, since that rewrites the check scripts.

@Snailedlt Snailedlt left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! ✔️
Thank you for the contribution, and making us aware of this issue! 🙇‍♂️

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants