Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 7 months ago

Pure HTML + CSS + JS

P
eMKa18•90
@eMKa18
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

  • Mayen•440
    @Mayen007
    Posted 7 months ago

    Great work on this! You're really on the right track, but there's always room to polish the design a little more. Let's dive in!

    1. Responsiveness

    You're doing a solid job with responsiveness, but I noticed that setting width: 100vw on the body/html can cause horizontal scrolling on small screens (like 375px and below). This happens because the browser sometimes includes the width of the scrollbar in the viewport calculation.

    To fix this, try one of these:

    • Option 1: Add this to prevent padding/margins from expanding the width:

      * {
        box-sizing: border-box;
      }
      

      This makes sure padding and borders don’t affect the total width of elements.

    • Option 2: You can switch to using width: 100% on both html and body, which avoids the scrollbar issue on smaller screens.

    These small tweaks will clean up the horizontal scrolling problem and keep the design nice and responsive!


    2. Submit Button

    You're doing great with your button, but I noticed a noticeable white border that isn't in the design. This can be easily fixed by removing the border:

    button {
      border: none;
    }
    

    That'll bring it more in line with the intended design!

    Keep up the awesome work—you're doing fantastic! These tweaks will only make it even more polished.

    Happy Coding!

    Marked as helpful

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