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

Frontend Mentor - Interactive rating component solution by Emmanuel

gsap
Emmanuel-Xs•80
@Emmanuel-Xs
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


After selecting a rating, I want to be able to remove it after selecting it again

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Eileen dangelo•1,600
    @Eileenpk
    Posted about 2 years ago

    Hi Emmanuel! your project looks really good, I love how you used gsap for the animation, it was a really nice touch.

    To be able to remove the active class if a rating is already selected add this code

    ratingsContainer.addEventListener("click", (e) => {
    	if (!e.target.matches(".rating")) return
    
    	// Check if the clicked rating button already has the "active" class
    	let alreadyActive = e.target.classList.contains("active")
    
    	ratings.forEach((rating) => rating.classList.remove("active"))
    
    	// If the clicked rating button was already active, remove the "active" class and return
    	if (alreadyActive) return
    
    	let selectedRating = e.target
    	selectedRating.classList.add("active")
    	let selectedRatingValue = selectedRating.textContent
    
    	// Rest of the code...
    })
    
    

    Also, consider moving the button.addEventListener() outside the ratingsContainer.addEventListener() to avoid creating a new event listener every time a rating is clicked.

    Hope you found this helpful!

    • Let's connect on LinkedIn! - @Eileenpk
  • Emmanuel-Xs•80
    @Emmanuel-Xs
    Posted about 2 years ago

    Okay, let me try your solution out. I created the button eventListener inside the inputs to ensure the user clicks a rating before submitting without writing extra code. However, from what you said, it creates multiple click events for the button that may slow down the browser's overall speed. So, I will do as you say.

    Thank you very much I tried it and it worked. I really appreciated

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