Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 3 years ago

Interactive Rating Component with JavaScript

Dummy_ken•180
@DummyKen
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Help! :) I cannot toggle back the rating numbers 1-5 back to its original state. And I need a little tweaking in mobile. Any help appreciated!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Gugg•130
    @Gugg94
    Posted about 3 years ago

    Hey,

    1. I'd suggest using similar naming in HTML and JS, now you're mixing i.e. "numbers" and "ratings" for the same element, that's a bit confusing. I'd also be consistent in formatting and/or installing a code formatting plugin

    2. You've added the event listener for selecting a rating on the "ratings" container, which seems to add it to the container itself AND the items inside, resulting in being able to select the container if you click between the numbers, this is not what you want. Don't forget you also have "querySelectorAll" to select multiple elements, you should use this so you can select all the ratings items: => "const ratings = document.querySelectorAll('.number');" You can remove the selector for the container "numbers", you don't need that.

    3. Once you have all the separate numbers, you can add an event listener to all of them using a for-loop or forEach, you can look that up to figure it out.

    4. If you want to return a previously selected element back to it's original state you have to ask yourself "when will I reset the selected state?", the answer will be "when I select a number" => in your event listener, BEFORE you select a new rating, use a for-loop or forEach to go over all the numbers and remove the selected state, once they're removed everywhere you can safely add the selected state to the correct element

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, SASS, 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