Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

NFT card - Hover effect, Flexbox

John•410
@MiyaoCat
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I couldn't figure out the hover effect so I'm submitting now to see other people's solutions.

I was able to get the view-icon with the background-color to appear on hover, but the icon is too big and the opacity too strong.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Venus•1,790
    @VenusY
    Posted over 1 year ago

    Well done on completing this challenge!

    I saw that you fixed the issue with the view icon by adding padding: 7rem to .overlay-icon.

    While this works on larger screen sizes, if you shrink the viewport's width enough, I found that you start running into overflow issues because the padding + width of the view icon won't fit within the card.

    The initial cause of your issue with the view icon was this bit of code here:

    .nft img {
      width: 100%;
    }
    

    This combinator selects every descendant img element of .nft, including those that aren't direct children.

    In your case, this includes the view icon, which means the width of the view icon was set to 100% as well.

    To fix this, you can make one small change:

    .nft > img {
      width: 100%;
    }
    

    This ensures that you're only selecting direct children of the .nft element.

    You can now remove padding: 7rem from .overlay-icon.

    After doing so, you'll find that you run into the problem of the overlay no longer spanning the entire height of the NFT image.

    You can fix this by simply adding height: 100% to .overlay.

    Finally, you can add display: block to the NFT image to remove that small bit of whitespace underneath the image that you may have noticed.

    Other than that, well done once again for completing this challenge! You did a great job at replicating the design.

    Hope this has been helpful! :)

    Marked as helpful
  • John•410
    @MiyaoCat
    Posted over 1 year ago

    Thank you so much! That was incredibly helpful! I was wondering why the .overlay was appearing so big.

    Do you know why the bit of whitespace appears at the bottom if I don't do display: block to the NFT image?

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub