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

interactive-rating-component

Greta Vasiulyte•20
@great1greta
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  1. i tried to introduce if-else statement so the page would not load if the rating is not selected:

submitButton.addEventListener("click", () => {

if (evaluation) {

receiptContainer.classList.remove("hidden");

mainContainer.style.display = "none";

} else {

receiptContainer.classList.add("hidden");

} });

but it didint work and i couldnt come up with another way to do it. i looked up other peoples solutions for inspiration, but they all looked so complicated and unreasonably long.

  1. apparently, i suck at responsiveness. this is a second project that i fail to adjust it to a mobile device.
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ozmar Mendoza•240
    @ozzy1136
    Posted over 2 years ago

    Great job with this one!

    Strictly related to the question you asked, I think it would be easier to use radio buttons instead of regular buttons. This way, you can check if a value was submitted for the rating. This solution uses the FormData API, which has great browser support.

    A simple example:

    // index.html
    ...
    <form>
      <label>1
        <input type="radio" name="rating" value="one" />
      </label>
      // More radio buttons with labels
      ...
      <input type="submit" value="Submit" />
    </form>
    ...
    
    // app.js
    const formEl = document.querySelector("form");
    formEl.addEventListener("submit", (e) => {
      e.preventDefault();
      new FormData(e.target);
    }
    formEl.addEventListener("formdata", (e) => {
      // e.formData is a JavaScript iterator object, so you have to loop over it
      // data will be in the form of [name, value]
      // You could also do for (const [name, value] of e.formData) {...}
      for (const data of e.formData) {
        if (data[0] === "rating") {
          // There was a rating button selected
          ...
        }
      }
      // There was not a rating button selected
      ...
    }
    

    Check the MDN Web Docs for more information about FormData. Using radio buttons with labels also takes more effort to make the buttons look how you need to, so I would suggest you look for guides that go over this.

    I imagine you could loop over the radio buttons on submit and test for a checked value instead.

    Marked as helpful
  • Lucas Berta•260
    @LucasBerta
    Posted over 2 years ago

    Hi Greta, the live page is not working so I can't check what's the issue with the responsivity, but I've seen you didn't use @media queries on your project.

    Try to search for "@media css" on google, you'll quickly understand it and will be able to implement it on your project for making it responsive.

    Also, try to replace all px units to rem units for a better responsivity patterns. https://www.aleksandrhovhannisyan.com/blog/62-5-percent-font-size-trick/#what-about-625percent

    I hope you find this feedback useful =)

    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