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

Interactive rating component

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

Solution retrospective


I had the help of a tutor to do the bit where you select the rating and it goes into the thank you card, any suggestion on where I can get documentation to look into it further-or any other way that could have been tackled is appreciated!!!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Osama Elshimy•140
    @Osama-Elshimy
    Posted over 2 years ago

    Nice Work!

    You asked for a way to implement the select rate part. Here is how I did it:

    • Give the span element an id or a class like you did, you gave it an id='rate'
    • Select the element in JavaScript:

    const rate = doqument.getElementById('rate')

    • Select all the button elements like you did my friend:

    const btns = doqument.querySelectorAll('.btn')

    • Add event listener to a common parent element btn-list
    document.querySelector('.btn-list').addEventListener('click', function(e)) {
    // Determine what element caused the event - what button was clicked
    const clicked = e.target.closest(".btn");
    
    // return if no button is clicked - if the user clicks on the list button but NOT on a button 
    if (!clicked) {
        return
    }
    
    // Assign the value of the clicked button to the span element
    rate.textContent = clicked.textContent // No space 
    
    // You can add space before the number by using bracket notations like this:
       rate.textContent = ` ${clicked.textContent}` // There is a space
    }
    }
    
    • Final step: When you click the submit button. You have to make sure that the user chooses a rating:
    // return if NO rating was chosen - No button is clicked
    // If no rating was selected, then the value will be null
    if (!rate.textContent) {
       return
    }
    

    The UI is very nice, but you must improve the semantic HTML. Use form instead of ul

    If you need more help on the JavaScript part, feel free to reply and I'll be glad to help.

    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

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