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

Tip calculator

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

Solution retrospective


Any comment or advice is helpful. Have a nice day.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dev Rathore•2,540
    @GitHub-dev12345
    Posted over 3 years ago

    Congratulation 🚀😁 complete your challenge. Used this code want your card in center position :

    in body tag Used this CSS Code: body{ display : flex; justify-content: center; align-item: center; }

    in Card Design CSS Code used this property: align-self: center;

    Marked as helpful
  • Account deletedPosted over 3 years ago

    Hello there! 👋

    Congratulations on finishing your challenge! 🎉

    I have some feedback on this solution:

    • Always Use Semantic HTML instead of div like <main> <header> <footer> , etc for more info
    • Form elements must have labels
    • add to the reset button cursor:pointer; so that the users know its clickable

    i hope this is helpful and goodluck

    Marked as helpful
  • Anton Sukhadolets•330
    @SuhodolecA
    Posted over 3 years ago

    Hello! Not a bad solution! Also, I have some tips for improving your result:

    1)For left-side p, use "font-weight" property and another "color". This will make your solution look more like a layout. And reduce padding till 5px;

    For example:

    .left-side p {

    padding: 0 0 5px;
    margin-top: 20px;
    font-weight: 700;
    color: hsl(186, 14%, 43%);
    

    }

    2)When I click .input-num all things inside twitch. It happens so you change the input side by adding a border. You can fix this, but you need to change your approach. Add a border to this input in general styles and set "color": transparent and then change only color but not border. Then use :hover and :focus pseudo-classes for triggering. And add "transition property for smooth animation", add this property for all elements where you want smooth animation. Also add "cursor":pointer.

    For example:

    .input-num {

    border-radius: 5px;
    min-height: 30px;
    text-align: right;
    font-family: "Space Mono", sans-serif;
    background-color: hsl(185, 41%, 84%);
    border: 1px solid transparent; 
    transition: all 0.3s linear;
    cursor: pointer;
    padding: 5px;
    

    }

    .input-num:hover {

    border-color: hsl(172, 67%, 45%);
    

    }

    .input-num:focus {

    border-color: hsl(172, 67%, 45%);
    

    }

    1. <input class="input-num" type="number" id="bill-num" value="0" onchange="getBill(this)" />

    Replace value = 0 on placeholder="0" and add style using pseudo-class :placeholder;

    For example:

    <input class="input-num" type="number" id="bill-num" placeholder="0" onchange="getBill(this)" />

    4)You can hide arrows in .input-num using next code:

    .input-num::-webkit-inner-spin-button { -webkit-appearance: none; }

    That is only part of the changes but if you use this your solution will be better!

    You are doing well, have a good day!

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.

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