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

css(puro) e JavaScript(puro)

Diego Imperiano•60
@DiegoImperiano
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I used pure CSS and pure JavaScript in this application to practice the basics of programming. Any constructive criticism will be very welcome to improve this application in the future.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Larry•190
    @ljcutts
    Posted over 3 years ago

    Nice work! First for the tip calculator title, I would have used the logo.svg that was given to you in the image folder. I would also work on trying to center the whole tip-calculator container as it is on the original design. Maybe add some heavier weight to your font? I'm not sure what the R is there for in terms of the currency. As far as the 'No Tip" button, it should say "Custom" meaning the user can put in any tip% they want, say for example 11. On the desktop version on the left side with the bill inputs, I would probably add padding at the bottom to give some spacing like you have on the right side. For the mobile version, I would constraint the width(max-width, min-width) of the app more so that it doesn't keep adjusting as you make your computer window bigger. As far as the total amount for the calculations, it should be the bill + the tip amount. For example, if the bill is $100 and the tip amount is $25, the total should be $125. Hope this helps!

    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

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub