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

HTML, CSS and JavaScript

bem
Ali Ali•40
@alibeniaminali
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  • Feedback welcome

What did you find difficult while building the project?

  • I wasn't able to add the background colour when the input is :checked. I tried using CSS but it didn't work. I am guessing is because I wrapped the input type in a label tag so when the user clicks the number it also checks the input.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • mahen2-cmd•150
    @mahen2-cmd
    Posted almost 2 years ago

    Great Job Ali!

    I just solved the challenge with the background color changing when the input is :checked. You might want to look at my solution.

    https://www.frontendmentor.io/solutions/interactive-rating-component-solution-using-html-css-and-javascript-iGOlR8A7xn

    Here is what I did:

     {
                button.addEventListener("click", function() {
                  if (selectedButton) {
                    selectedButton.classList.remove("highlight");
                  }
                  button.classList.add("highlight");
                  selectedButton = button;
                });
              });
    
    
    

    and added css

    .highlight {

    background-color: hsl(25, 97%, 53%);
    color: white;
    

    }

    Now, whenever a button is clicked the .highlight css is activated and it would change the color of the button.

  • P
    Amy Spencer•360
    @amyspencerproject
    Posted almost 2 years ago

    Good Job Ali!

    I remember having some of the same issues with the :checked. In the end I took my <input> out of the <label> div for accessibility reasons. And then just used adjacent sibling combinators to get my :hover and :checked. Like this input:checked + label { background-color: var(--light-grey); }

    Did you try combining the label and input?

    label input:checked { background-color: red; }

    or maybe

    label > input:checked { background-color: red; }

    The Stephanie Eccles article I used as a resource has a solution that also might work for you. And she has the <input> nested into the <label>. Step #4 https://moderncss.dev/pure-css-custom-styled-radio-buttons/

    Hope this helps you. Amy

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