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

interactive rating componenet

accessibility
Aiyegbajeje Yusuf•100
@devsilvar
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


i Struggle to refator my javascript. i dont know how to select one of the buttons in the div box while making it turn orange.

EG i have 5 button the users can hover above. BUt when they select one it tuns orange ... now if they decide to select another button without clicking submit. it doesn't turn orange again.

just like a review stuff, that one can change from 2 to 5 start without refresigng the page

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hi AIyegbajeje, this is a good try I think! I'm looking at your code, and it seems like you are writing an event listener for each button individually, and then writing out the change in inline style for each button also individually, which could easily give you errors when you're repeating so much code. What I suggest is to use a style class (maybe called active or selected) that you can add and remove to your button whenever something is clicked. Using inline styles the way you did could also be the reason why the button doesn't turn orange when selected again. Also, it would help to use for loop or even a forEach to loop through the buttons; then you don't have to write each out one by one!

    Here's a CodePen I have for this challenge that might give you some ideas on how to solve this problem: https://codepen.io/elaineleung/pen/RwMqMxZ

    Good luck!

    Marked as helpful
  • HinaSejaru124•310
    @HinaSejaru124
    Posted almost 3 years ago

    Hello if you could remove the <eb> tag and add HTML Lang="en" and avoid using inline styling it would be perfect, when added to what you have already done

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