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

Interactive rating component solution -- Radio Buttons with Plain JS

Ting-Huei Chen•180
@hejkeikei
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback will be much appreciated :)

How I did it:

  • I loop through all the radio button and pass the iterative object to query selector to dynamically get the option that user select.
  • Get user's input value when the submit button have been click on then show it in DOM.

Question: I would like to try to go with object oriented way such as event target to select an element in the group so that I don't have to write loops all the time. If anyone know please tell me I'll be super thankful.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Hariz•100
    @sj0n
    Posted about 3 years ago

    Instead of attaching click event on all the buttons, you could just bind submit event on the form element. When submitted, the form element will contain the data binded on the name from the input element. You could then use FormData function to parse data from the form element.

    You can check out my solution if you need an idea on how to solve this challenge.

    [1] https://developer.mozilla.org/en-US/docs/Web/API/FormData/FormData

    Marked as helpful
  • Carlos Damian Perez•1,930
    @caarlosdamian
    Posted about 3 years ago

    Hello, You can try using git repository and upload your page to Github pages your code looks great overall but just that little comment, GitHub will allow you to allocate all you projects and applications with a free hosting https://pages.github.com/ its very easy to upload just create a branch with the name gh-pages and GitHub will automatic upload your pages ,

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

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