Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

html css javascript

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

Solution retrospective


my javascript is disgusting it works a bit close but help me do it better thank you in advance

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adriano•42,890
    @AdrianoEscarabote
    Posted over 2 years ago

    Hello mclanecorp, how are you?

    I will help you make your code much smaller!

    I noticed that you used an event for each button, we can reduce this a lot by getting all the buttons in just one variable! But first, let's make some changes to the HTML!

    <span id="1" class="btnRate">1</span>

    I changed the name of the classes of all the buttons to the one above.

    ok, now let's go to js:

    We will remove all selecteur events and variables will be removed from the code, then we will add this:

    const btnRate = document.querySelectorAll(".btnRate")

    and I will add something called forEach in that variable that we store all the buttons, so our forEach method will loop in each button, and we will pass as a parameter a function that will work on each element!

    this function will have the addEventListener of type click, and this event will work on all buttons:

    btnRate.forEach((element) => {
      element.addEventListener("click", () => {
        element.classList.toggle("isactive");
        const sum = element.innerText
        document.getElementById("choix1").innerHTML = sum;
      })
    })
    

    I hope it's clear!

    The rest is great!

    Marked as helpful
  • Account deletedPosted over 2 years ago

    Hey there! 👋 Here are some suggestions to help improve your code:

    • Change width to max-width in your component’s container to make it responsive. You will also want to delete the height as it is unnecessary.

    • The icons in this component serve no other purpose than to be decorative; They add no value. There Alt Tag should be left blank and have an aria-hidden=“true” to hide them from assistive technology.

    • Add a cursor: pointer to the “”rating buttons to improve usability of the buttons.

    • The proper way to build this challenge is to create a Form and inside of it, the “rating buttons” should be built using an Input Radio and it should have a Label Element attached to it.

    If you have any questions or need further clarification, feel free to reach out to me.

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub