Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Icons in the FeatureCard have became blue #883

Closed
xylish7 opened this issue Jun 22, 2020 · 2 comments · Fixed by #891
Closed

Icons in the FeatureCard have became blue #883

xylish7 opened this issue Jun 22, 2020 · 2 comments · Fixed by #891

Comments

@xylish7
Copy link
Contributor

xylish7 commented Jun 22, 2020

Detailed description

Describe in detail the issue you’re having.

Upgrading to the last version of carbon (1.24.4) the icon of the FeatureCard became blue.

What did you expect to happen? What happened instead? What would you like to see changed?

  • Expected look:

image

  • Current look:

image

What browser are you working in?

  • Firefox
  • Google Chrome

Steps to reproduce the issue

  1. Run npx gatsby new my-carbon-site https://github.com/carbon-design-system/gatsby-starter-carbon-theme
  2. Change this packages to this versions in package.json:
    • "gatsby": "^2.23.8",
    • "gatsby-theme-carbon": "^1.24.4",
    • "react": "^16.13.1",
    • "react-dom": "^16.13.1"
  3. Run yarn
  4. Run yarn dev -> the icon become blue in FeatureCard on light type
@sstrubberg
Copy link
Member

Works just fine for me.

  1. I ran npx gatsby new my-carbon-site https://github.com/carbon-design-system/gatsby-starter-carbon-theme
  2. I then ran yarn add gatsby gatsby-theme-carbon react react-dom to upgrade all the packages.
  3. Ran yarn dev. Rock n' roll!

image

@xylish7
Copy link
Contributor Author

xylish7 commented Jun 23, 2020

@sstrubberg yes, but this is a dark card, not a light one. Try with a light one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants