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

Tip Calculator with colour slider at bottom using CSS/JS

feelgooddd•400
@feelgooddd
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'm proud of writing logic that works and is functional without having to consult any examples for this project.

Next time, or even in the future I'd like to refactor this code to use Queryselector on my tip buttons and loop through them to add functions & event listeners rather than manually writing out 5 separate functions for each button and then using the buttons onclick method in the HTML to call those functions.

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

One issue I had throughout the entire project was keeping the text in the output section from breaking up when the numbers were of different lengths such as the tip amount / person being $x.xx and the total amount / person being $xx.xx i would run into issues with the Text to the left of it splitting up and ruining the aesthetic. The issue was using 2 separate <p> takes one for the 'Tip Amount' and another for the '/person'. I fixed this by putting 'Tip Amount / person' in a single <p> tag with a <br> to line break and a span tag around the /person to style it.

Another issue I ran into was not being able to access and change numbers for multiple variables in my CSS. I used typeof to find out I was trying to work on strings as if they were numbers, and I fixed it by converting them to numbers using Number and parseFloat.

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

I don't think the way I did the colour scheme change was the most efficient. I used Javascript to record all of the colours in my CSS :root variable as JS variables and then changed them within JS. If you have another way for me to change the colour scheme then please write a message telling me how you would tackle this.

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 feelgooddd'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.