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

i only use vanila javascript,html and css preprocessor (sass)

sass/scss
Rio Rifaldi•100
@rio-rifaldi
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


i just wanna know from you guys about this project.

how do you set the counter of user`s rating input? my first idea is using an empty array and then export the value from index.html to another page of thank-you(thanks.html in my case). but i getting stuck when i try to export the value. javascript showing an error that there is an null value (submit button) on index.html. seems like javascript guess all of instruction of index.html is getting included to thanks.html so its showing an error.

finnaly i using localstorage,an alhamdulillah its works like i expected

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Caleb•320
    @calebQWEB
    Posted almost 3 years ago

    Hi Rio

    great job on the layout, first off you could store the user's rating input in an empty array or an empty string, in my case I used an empty string and then set the length of that string to always equal 1 if it doesn't equal 1 I used the .slice() method to remove the first item in the string.

    and then secondly instead of having a separate file for the thank-you section, you could have it in a separate container in your index.html and set it to display : none and then set an event listener on the submit button to display the container and hide the rating section whenever you click it.

    I hope this was helpful 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