Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Interactive rating component (HTML, CSS, and Vanilla Javascript)

solvman•1,650
@solvman
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Venus•1,790
    @VenusY
    Posted over 1 year ago

    I'm posting this as a separate comment and not a reply in case you find this helpful.

    After clicking a rating button, it turns a lighter grey, which indicates that the user has selected that rating. This is fine and expected.

    However, clicking off the button causes it to go back to its default styling, which suggests that it's no longer selected, but pressing the submit button will cause the page to proceed to the 'thank you' page with that rating anyway.

    I see you have an event listener that changes the innerHTML of the rating message on the 'thank you' page when the user clicks on a rating button:

    rates.forEach((rate) => {
      rate.addEventListener("click", () => {
        rating.innerHTML = rate.innerHTML;
      });
    });
    

    I suggest listening for a click outside of a rating button (and also not on the submit button) to reset the rating.innerHTML back to "" to make the functionality of the page more intuitive.

    Alternatively, you could make it so that the button does not appear to lose focus upon clicking off it, which might be an easier approach.

    Hope this helps! :)

    Marked as helpful
  • Sardor•110
    @sardorw
    Posted over 1 year ago

    Nice work

  • Venus•1,790
    @VenusY
    Posted over 1 year ago

    Great work! This is a really good solution to this challenge. The buttons work well, and the styling very closely resembles the design mockups, so well done.

    However, one thing I would point out is that the body's height property is set to 100vh, which causes some issues when the screen size is too small to fit the entire card vertically. In other words, when the height of the card is greater than the height of the viewport.

    A simple fix for this is changing height to min-height and leaving the value at 100vh. This will make the body take up the entire viewport height while still letting it expand if necessary.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub