Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

Frontend Quiz with Dark/Light Theme

bem
P
Purnama S Rahayu•250
@catreedle
A solution to the Frontend Quiz app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am just glad this is done but the code is rather messy. I should've planned this better and need more practice writing clean codes. I also like the chance to learn how to use theme with CSS and make elements navigatable with the keyboard.

What challenges did you encounter, and how did you overcome them?

Many details go into this project, making it challenging to keep the code clean.

What specific areas of your project would you like help with?

There's a bug that sometimes the toggle doesn't work with the keyboard. If you could help me figure out why that is, that'd be great haha.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    markus•2,760
    @markuslewin
    Posted 11 months ago

    Hey!

    The clickOnKeyPress function adds an event listener to the theme toggle every time the function is called. Since the function is called every time a question is set up, the toggle will have multiple event listeners, and so one click will toggle the theme multiple times!

    I'd use a <button> element for this toggle, but another solution would be to create a unique setup function for the theme toggle. It shouldn't need the || event.key === " " part of the function since the browser handles space presses by default.

    Marked as helpful
  • P
    MikDra1•7,450
    @MikDra1
    Posted 11 months ago

    WOW! Your app looks amazing!

    One thing that I would change is in the question in JavaScript about for loop. We don't have to but we can do sth like down here:

    We just add the let keyword (it's not a must have)

    NOT: for(i = 0; i <= 10; i++);

    BUT: for(let i = 0; i <=10; i++);

    Hope you found this comment useful 💗

    Good job and keep going 😁😊😉

    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