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

Tip Calculator (Not Completed)

Cody•170
@Cod-Bigg
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I know this is not completed, but I asked questions about this on a few forums and have not heard back yet. I will update solution when I get it completed.

  1. What is the custom button? Is that an input?

  2. I could not get the white background behind both sections. I tried adding another div that included both of the sections, but it caused issues

  3. the red text on the active state section. Is that made by creating an element? I know you would have to check the input value and if it is zero would I create a span or something?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rio Cantre•9,650
    @RioCantre
    Posted over 3 years ago

    Hello there! base on the issues you've written I could try make some suggestions:

    • The custom button is not a button, it's an input with a placeholder="Custom" where the user can input random numbers.
    • To add the whole content with the same background, you could try to adjust the css property of the designated classes... for example:
    tip-flex-container {
      display: flex;
      flex-direction: row;
      height: 600px;
      align-items: center;
      justify-content: center;
      border-radius: 20px;
      background: white;
      width: 900px;
      margin: auto;
      margin-top: 3rem;
    }
    

    Add the width, margin, margin-top to wrap the whole content and eliminate the border.

    • Adjust the other content as well like inside the .calculating-bill rule set, eliminate the border, background-color and border-radius
    .calculating-bill {
      width: 400px;
      height: 500px;
      flex-wrap: wrap;
      padding: 30px;
    }
    
    • The borders of the button and input tag should display into none.

    From here I think you can adjust the values and make more improvements. I hope this is helpful.

    Marked as helpful
  • Matthias Wagner•330
    @MatzeW95
    Posted over 3 years ago

    To your first point. The custom "button" Is not a button. It is an input field for a custom value.

    Marked as helpful
  • Cody•170
    @Cod-Bigg
    Posted over 3 years ago

    Got it! Yeah, I got the calculations working correctly. I was just confused since I di not see a total button in the design, but I guess running the calculation after the tip selected makes sense. Appreciate the help!

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

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