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

Interactive Rating Component using Bootstrap CSS

bootstrap
whitehatns•150
@platypus567
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Not sure how to make it deselect a button when another is clicked, any advice would be very helpful! Still stuck on that.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Priya Aggarwal•160
    @pa-aggarwal
    Posted about 3 years ago

    Hey,

    Your solution looks good and it responds appropriately to the screen size which is great!

    For your question about how to deselect a button when another is clicked, instead of using the <button> element for the ratings from 1-5, you can use multiple input[type="radio"] elements and give them the same name attribute. This basically allows only one item to be checked at a time.

    I hope that helps answer your question :)

  • Umair•240
    @umairanwer
    Posted about 3 years ago

    A good solution to your problem is already provided. There is another solution to this issue, if you want to use <button>.

    • In your CSS create styles for a class "selected-btn"
    • Set the styles of this class to the ones you selected in your js code (background-color and color). And remove them from js code.
    • Now whenever a btn is clicked, first loop through all the buttons and remove 'selected-btn' class from them.
    • After this add the 'selected-btn' class to the clicked button.

    Hope this helps. Feel free to ask any questions.

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