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

interactive-rating-component

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

Solution retrospective


Eager to have your feedback on my JS, surely there is a way to write less code

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sahiru•220
    @bhatsahil13579
    Posted over 2 years ago

    Nice job cryptososso 😀

    Here are some feedbacks

    Your all buttons are having borders you can remove them simply by adding ( border : none)

    In Js Part :

    i see that you have added event Listener for each button separately but you can do it by only adding event Listener one time through ForEach method like this :

    btn.forEach(elements => 
       
    elements.addEventListener("click", () => {
    }
      })
    

    but make sure you have selected that element by querySelectorAll

    and also there is no need for score1 , score2 like that you can simply do it like this :

    btn.forEach(elements => {``
       
    elements.addEventListener("click", () => {``
       
     rateScore.textContent = elements.textContent
    }
     })
    

    and i can click submit button without submitting rating to stop that add disabled attribute to your all rating buttons and then in js you can remove that attribute if the click is true like this

    btn.forEach(elements => {
       
    elements.addEventListener("click", (task) => {
         
    rateScore.textContent = elements.textContent
        
     if (task) {
        
    btn.removeAttribute("disabled"  )
          }
    
       })
    }
     }) 
    

    hope it will help you 😀😀

    Marked as helpful
  • Account deletedPosted over 2 years ago

    Hey there! 👋 Here are some suggestions to help improve your code:

    • The “icons/illustrations” in this component serve no other purpose than to be decorative; They add no value. There alt tag should be left blank and have an aria-hidden=“true” to hide them from assistive technology.

    More Info:📚

    https://www.w3.org/WAI/tutorials/images/

    • The proper way to build the "rating buttons" in this challenge is to create a form and inside of it, there should be fiveinput radios and each input should have a label attached to it to make the buttons accessible. Finally wrap all the inputs and labels inside a fieldset to prevent users from making more than one selection.

    More Info:📚

    MDN <input type="radio">

    MDN <fieldset>: The Field Set element

    If you have any questions or need further clarification, feel free to reach out to me.

    Happy Coding!🎄🎁

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