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

Vanilla JS & SASS

sass/scss
P
Nate Valline•420
@nvalline
A solution to the Tip calculator 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 decided to go above and beyond and add an error 'toast' on the bill input as well to indicate that it cannot be a negative number.

I also got a better understanding of parseInt and parseFloat. I have used parseInt several times, but never really considered the differences with parseFloat.

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

Styling the radio buttons was my biggest challenge as I have never done that before. Luckily the 'all knowing' Google was able to provide me with the correct info.

I also wanted to format the Bill and Number of People inputs to not allow negative numbers or more than two decimal points for the bill. I was not able to find a solution that worked properly.

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

If anyone knows how to structure the inputs to not allow negative numbers or to limit them to 2 decimal points that works for this app I would be interested in learning that.

Also I always appreciate any tips/suggestions to improve the quality of my code.

Thanks!

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 Nate Valline'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 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.