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

Interactive Rating Component

P
Darkstar•1,440
@DarkstarXDD
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Built with. 🔨

  • HTML & CSS.
  • JavaScript.
  • Vite.

Features. ✨

  • Display a custom error message if a rating is not selected when submitting.

New Things Learned. 🎓

  • Custom styling radio buttons.
  • attr() CSS function - Used to retrieve the value of an attribute of the selected element and use it in the stylesheet. - MDN
  • Next-sibling combinator (+) - Matches the second element only if it immediately follows the first element. - MDN
What challenges did you encounter, and how did you overcome them?
  • The main problem was how to make the radio buttons look like the design. After searching and playing around for sometime I had two methods.

    • Method 1: Visually-hide the radio button and style the label to look like the radio button. Based on the radio button's focused or checked state, the label can be styled.

      .radio-button:focus-visible + .radio-label {
        outline: 0.125rem dotted var(--clr-primary-400);
        outline-offset: 0.125rem;
      }
      
      .radio-button:checked + .radio-label {
        color: var(--clr-primary-600);
        background-color: var(--clr-primary-400);
      }
      
    • Method 2: Visually-hide the label and style the radio button to get the desired look. With this approach I had to use an absolutely positioned pseudo element to display the number in the middle of each radio button.

      .radio-button::after {
        content: attr(value);
        position: absolute;
        top: 50%;
        left: 50%;
        transform: translate(-50%, -50%);
      }
      
  • I ended up using the first method.

What specific areas of your project would you like help with?

Any sort of feedback is appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Filip Stojkov•550
    @thentrsfs
    Posted 10 months ago

    It is very precise, i like it, good job keep it up!

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