Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

Tip Calculator in Vanilla JS and HTML

K MacLeod•40
@ksmacleod99
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any good reading on styling ONLY active/selected buttons, and returning previously selected buttons to a non-selected style? I gave up :(

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, ughm. Did you code on this on a large screen? The layout for me is bad since it is really big. But zooming out, the layout seems kinda nice, just the size needs to be fixed for other screen resolutions. The mobile layout is good, just needs a little bit of padding to the left and right side of the body to prevent it from touching the sides.

    Regarding your concern, Conrad already said a great tip about that. But let me explain it a bit more. Well to be more clearer, I'll just create a small snippet that you can look. If that is your desired outcome, if it's not, just drop it here and maybe I can help with it.

    Some suggestions would be:

    • Of course first, make the layout be good and responsive in other screen resolutions as well and not only for large screens.
    • You don't really need to adds stylings on the html element. Typically, on the html element, you would just see these stylings:
    html {
      box-sizing: border-box; # or any other box-sizing values
      font-size: 100%;
    }
    

    Instead of applying it on the html element, apply it on the body tag.

    • The .container selector that holds the tip calculator itself, I would not recommend position: absolute on it. Leave it on the flow. If you try to inspect your layout in dev tools, hover on the body tag. You will see that the body have a small dimension and doesn't really captures the calculator itself. That is the effect of position: absolute.
    • A website needs to have at least 1 h1 tag. On this one, it could be the "SPLITTER" text, or it could be a screen-reader only text.
    • On the input of the calculator, on the bill. You can see that when it has focus, it shifts a bit the elements at the bottom, this is because you are adding a border to it right. To make it not do that, make the element already have the border but the color of it is transparent. It would be like: border: 3px solid transparent and when it have the focus just transition the border-color. This way it won't shift the element. You can apply this on other input elements on your solution.
    • I think that the logic on your tip calculator is not correct? Checking that one out would be really great.
    • This challenge could have used more accessibility features, but if you are starting out, it's fine, but as you go along, remember to add accessibility as a goal on websites.

    Other than those, great work.

  • Conrad•930
    @ConradMcGrifter
    Posted almost 4 years ago

    You can make a css class with the active styles and then toggle it on and off with javaScript

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.

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