Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 days ago

Interactive rating component

Farzaneh•50
@Farzane2630
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

  • P
    Katrien Schuermans•1,420
    @katrien-s
    Posted 9 days ago

    Hi, it overall looks good but there's some minor issues.

    I can click on all buttons, have them all highlighted before I click on submit. You should limit this to have only one button highlighted.

    It's advised to combine all css in one file. There's no need to split it up. The same for your javascript. You can have it all in one file.

    There is also no need to set a width on your body. It always takes by default 100vw.

    Why did you use !important so often? Check also if by adding all your css to seperate classes, you maybe wrote too much css.

    For example: .icon-wrapper and .thanks-icon-wrapper seem to have the same flex-styling which you could maybe put on section instead of adding the same code to 2 classes, that have the same use/outcome.

    But great job on this one. The Javascript works well, and it does what it needs to do. Have a look at the things I pointed out, and keep coding.

    Marked as helpful
  • RG-07•70
    @RaviGahire
    Posted 5 days ago

    Good work, I just tested it..

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