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

css grid, React Cookies, Media queries, React Hooks

Marcel•110
@Marcelckp
A solution to the Calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I have/had no idea how to even begin making the button slider under the theme selection, if you could direct me to any resources to help because I don't even know what the component is called so I had trouble looking for it on google, Thank You again!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tamera•110
    @tlbodrick
    Posted over 3 years ago

    Hi, Marcel!

    If you look up tri-state toggle/switch, you should find some good resources for it. The way I did it is I used hidden radio buttons/labels within a styled div to produce the effect. I used another div to make the circle button as well, and had it hide or show depending on which "theme" (label) I was clicking on.

    Other people don't make the circle clickable, just the numbers, and then have the circle button show/hide depending on the button clicked on. It all depends on what you want!

    Feel free to check out my solution if you like! Good luck.

    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