Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Interactive rating component

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

Solution retrospective


Hi ! I got an issu with my JS. on the click it takes my to the page thank.html but it doesnt change the rating counter.

I don't now how to fix this..

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Daniel 🛸•44,790
    @danielmrz-dev
    Posted over 1 year ago

    Hello, Julien!

    Your project looks great.

    I'm also learning JS and this challenge gave me a hard time too 😅

    I'm not sure how to fix your issue, but I'll tell you what I've noticed that's different from my solution.

    I worked with two pages too. Then I set my javascript to switch between them when submit is clicked. But I also had the selected number in the HTML wrapped with a span tag. Then, when the number is selected and submitted, javascript place it inside my span tag.

    Here's what I did:

    if (inputnotas[0].checked) {
            nota = 1
            section01.style.display = 'none'
            section02.style.display = 'flex'
            rate.innerHTML = '1'
    }
    

    Where inputnotas is the number, section01 is the rating page, section02 is the Thank you page, and rate is that span tag that I told you before.

    I know that does not solve your problem, but I hope it helps you!

  • JulienLach•260
    @JulienLach
    Posted over 1 year ago

    Maybe because i made 2 pages ? Instead of one with the 2 containers? I dont know if javascript works with multiple pages like this

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