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

Microsoft Windows Calculator Clone w/ Vanilla HTML CSS Javascript

Specticall•370
@Specticall
A solution to the Calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


The functionality of this calculator is based of window's native calculator app.

This had to be one of the most difficult projects I've done in the last 4 months of me learning to program. There are quite a few troubles I came across during to projects :

  1. The built it in number formatting system, toLocaleString() method, did not work at all for me. So I had to program my own number formatting function (it was quite a challenge)

  2. Some issues I also found is how different browsers display scroll in their own way. This makes it difficult to keep a consistent look cross browsers. The overflow scrollbar on the main display kept adding / reducing padding randomly in certain browsers and I honestly gave up trying to figure those stuff out haha.

  3. Getting the "." (comma) to work seamlessly and accounting for user errors are also quite a pain. This also became one of the reason the locale string method did not work, because it kept rounding my numbers down. So whenever the user input "0,0000" it would only display "0".

There are more things that I can mention however, I don't want this to be 100 paragraphs long so we're going to keep it at three. Also, I wouldn't be surprised if I missed some bug because it was very overwhelming!. In the end I had quite a lot of fun working on this and would love to keep doing more.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Specticall'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

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.