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

Interactive Rating Component

P
Øystein Håberg•13,260
@Islandstone89
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

With some work, I managed to get it mostly right.

What challenges did you encounter, and how did you overcome them?

The biggest challenges were styling the buttons, and figuring out how to get the values.

What specific areas of your project would you like help with?

The only issue now is that when you click right in the middle of the buttons, you get "You have selected undefined out of 5" on the thank you card. Each button is a ```` with a label and an input inside. I get the values from a data-value attribute set on the divs. I increased the padding on the mobile version to get a bigger target size.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Roksolana•910
    @RoksolanaVeres
    Posted about 1 year ago

    Hi! I have a simpler solution. You don't need a separate wrapper for label and input, instead you can wrap your input by the label itself:

    HTML:

    <label class="rating-btn-wrapper">
      <input type="radio" name="rating" value="1" class="rating-btn" />
            1
    </label>
    
    <label class="rating-btn-wrapper">
      <input type="radio" name="rating" value="2" class="rating-btn" />
            2
    </label>
    ...
    

    Now you don't need to use id and for attributes. Here you can read more about it:

    https://developer.mozilla.org/en-US/docs/Web/HTML/Element/label

    Now your button styles are broken. To make rating buttons completely round, just remove paddings and add fixed width and height for buttons:

    CSS:

    .rating-btn-wrapper {
        background-color: var(--clr-dark-blue);
        height: 45px;
        width: 45px;
        border-radius: 50%;
        ...
    
    Marked as helpful
  • Koda👹•3,830
    @kodan96
    Posted about 1 year ago

    hi there! 👋

    I would probably wrap the radio buttons and the labels into wrappers:

    <div class="rating-btn-wrapper" data-value="3">
              <label for="option-3">3</label>
              <input type="radio" name="rating" id="option-3" value="3" class="rating-btn">
    </div>
    

    and change the selector to target the input element directly:

    let ratingButtons = document.querySelectorAll(".rating-btn-wrapper input");
    

    so within your event handler you can retrieve the value directly:

    function ratingBtnClicked(e) {
        ratingButtons.forEach((button) => button.parentElement.classList.remove("active"));
        this.parentElement.classList.add("active");
    
        defaultScore = this.value;
    }
    

    Hope I got it right.

    Marked as helpful

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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