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

Interactive Rating Component

accessibility, webflow, tailwind-css
Satyam Jha•400
@satyammjha
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey, community this is my solution for the interactive rating component challenge. I have a few questions:-

  1. How to pop up a warning when the rating value is not selected?
  2. How to change the background color of the selected rating when another rating is selected It would be helpful if you could answer my questions. Other feedback is also appreciated.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Warren•650
    @warrenlee
    Posted almost 3 years ago

    Hey Satyam, looking at your code, in your submitbtn event listener for click I would check if selectedrating is defined/not empty before deciding to show the thank you message.

    For your second question in your function ratingdisplay you would typically do a reset before firing the selected state, and I would use classes and it'll make things easier and concise.

    What you have now is this.

    function ratingdisplay(event) {
      ratingbutton.forEach(() => {
        event.target.style.backgroundColor = "hsl(25, 97%, 53%)";
        event.target.style.color = "white";
        selectedrating = event.target.value;
      });
    }
    

    Firstly the forEach loop is redundant as it's apply the same styles to the same element, so instead I would use this forEach loop to reset the styles to what they were before and then apply the active state after.

    function ratingdisplay(event) {
      ratingbutton.forEach(() => {
        // reset your styles for each ratingbutton here
      });
    
      // apply selected state here
      event.target.style.backgroundColor = "hsl(25, 97%, 53%)";
      event.target.style.color = "white";
      selectedrating = event.target.value;
    }
    

    But if you use classes instead.

    function ratingdisplay(event) {
      ratingbutton.forEach((el) => {
        // reset your styles for each ratingbutton here
        el.classList.remove('selected');
      });
    
      // apply selected state here
      event.target.classList.add('selected');
      selectedrating = event.target.value;
    }
    

    Or even better still do comparison checks and use toggle instead.

    function ratingdisplay(event) {
      ratingbutton.forEach((el) => {
        // Use toggle to evaluate if the class should be added or removed
        el.classList.toggle('selected', el.value === event.target.value);
      });
    
      selectedrating = event.target.value;
    }
    

    Hope this helps

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