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

Interactive rating component with CSS & JS

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

Solution retrospective


I wonder what would be considered the true "best practice" way to pass the rating variable through. I also wonder if I'm saying that right. Also, I wonder how the JS that Eric helped me with could be simplified. Lastly, I wonder what sort of solutions people came up with to prevent someone from pressing Submit until a rating had been chosen.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Stefan RIZEA•120
    @JoyGHub
    Posted almost 3 years ago

    Hello Maia!

    When it comes to disabling the Submit button until a user selects a rating, in this case, your Submit could start by being disabled until the user selects any of the rating buttons (until any of them has the "clicked" class). After that, the user is 100% going to have a button selected, no matter what, so you no longer have to disable the Submit button.

    "Also, I wonder how the JS that Eric helped me with could be simplified." - Yes, they 100% can be simplified.

    Overall, the component looks great! I like the radial-gradient you placed on it.

    Keep it up,

    • Stefan RIZEA
    Marked as helpful
  • Eric Salvi•1,350
    @ericsalvi
    Posted almost 3 years ago

    Hey @maiaflow, great job on completing your 2nd challenge. We already had some offline communications about this one and I was glad you were able to do some digging into the JS to start the button actions but needed a bit of a push to get it completed.

    I know my code was not correct but was hoping you could use it as a base to elaborate upon it or to simplify it.

    The more you do of these the easier it will become. Keep on watching those teamtreehouse videos.

    I few suggestions now that you have completed this one, you have access to view all solutions of this challenge here. I would dig into the HTML structure of them to see if there are any common factors on how they implemented the interactive section of this challenge. I am not saying my approach to using a Form is the correct one, it just made it much easier and cleaner when it came to JS.

    Also make sure to clean up any HTML or Accessibility warnings of the submission here

    Keep up the momentum!

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.