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

Calculator App using javascript

‪Ahmed Gamal‬‏•320
@Ahmedabdalnaser2010
A solution to the Calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I’m excited to share my latest project: a Calculator App built with JavaScript. While it may seem like a simple project, I’ve added many features to make it more useful and practical:

1-Light Mode Toggle: Switch between dark and light themes for better visibility and comfort. 2-Backspace Button: Easily delete the last input to correct mistakes. 3-Bracket Buttons ( ): Help users perform more complex operations by grouping calculations. 4-Save Button: Save any result the user wants for future reference. 5-Equal Button: Calculate the final result and store it in history for easy access. 6-Ans | History Button: A single Click to restore the last saved result, and double-click to display the entire history, allowing users to select any result for reuse. 7-Reset/Clear Button: A single click resets the current input, while a double click clears all saved data from history. 8-Keyboard Support: Users can utilize keyboard keys for: a) Use number keys for digits. b) Utilize -, +, *, / for basic operations. c)Backspace key deletes the last input. d) Delete key to start anew e) Enter key to get the answer 9-Responsive Design: Enjoy a seamless calculator experience on any device, from desktops to smartphones.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on ‪Ahmed Gamal‬‏'s solution.

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.