Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 5 years ago

Article Preview Component with HTML, CSS, JS

Bhanu Teja P•470
@pbteja1998
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I was unable to make share icon color as white in mobile-active state. Any help on how to do that would be helpful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted almost 5 years ago

    Hi.

    The reason why you can't change the color of the icon is because you're using background-image and that is not part of the DOM, so you can't manipulate it directly. Fortunately, there are a few workarounds to solve this:

    1. Use mask

    Mask is a clipped image into specific points.

    .my-class {
         mask-image: url(my-image.svg);
         background-color: red;
    }
    

    As you can see, we clip the image and set a background color for that image.

    I wouldn't recommend this because it doesn't have good browser support (for instance, it doesn't work on IE and edge).

    1. Duplicate SVG (better solution)

    Create a new SVG image from the original one and change its fill value to #FFF

    When you hover the element, just replace the images

    .my-class {
        background-image: url(gray-icon.svg)
    }
    
    .my-class:hover {
        background-image: url(white-icon.svg)
    }
    
    1. Use font icons (best solution)

    Instead of using SVG, use font icons like IconMonstr or FontAwesome and treat the icons as fonts

    HTML
    
    <i class="my-class im im-fire"></i>
    
    CSS
    
    @import url("https://cdn.iconmonstr.com/1.3.0/css/iconmonstr-iconic-font.min.css");
    
    .my-class {
        color: #333;
    }
    
    .my-class:hover {
        color: #fff;
    }
    

    I hope it helps.

  • Zakarya Noori•0
    @ZakaryaNoori
    Posted almost 5 years ago

    pay attention to small details(shadows, alignment, font sizing and coloring) btw well done.

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