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

Interactive-Rating-Component

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

Solution retrospective


My first challenge using JS , feedback will be helpful

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nutchapon Makelai•270
    @kodaicoder
    Posted almost 3 years ago

    Hi Itaro, congratulations on completing the challenge 🎉 it's look good so far in desktop but in mobile it not so responsive and look not well may be you can checking out "Media Query" here to made a width of card responsive on mobile.

    Also my suggestion for rating section is to custom a input radio ( or checkbox) for that element instead of using a button element. check out how to create custom input radio ( or checkbox) here

    and may be you can check out my solution too here

    Marked as helpful
  • Kairat Kempirbaev•260
    @kairat-kempirbaev
    Posted almost 3 years ago

    Hi Itaro

    It looks perfect

    I am trying to improve design skills and would like to share a couple of observations. Hope those details would improve your solution:

    "* Out of 5" text can be aligned by base. This way padding from top/bottom would look even and elegant. On mobile phone the text doesn't fit in the specified background. "Selected" overflows the container.

    Looks nice. Mobile screen is quite hard to address sometimes, especially with custom components. Desktop version is perfect, i like 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

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