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

used html,css,JavaScript created static web page for tip calculation

accessibility, jss
Saravana Kumar•20
@Saravana16041999
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


while working on this project it was hard to align the ever thing in order for mobile view. and there are some mistakes in mobile view it might be good on 320px not on 425px . first time used onclick event in this project and used event listener "change" in custom option . custom is created using the input element. and claculation might be different i did based on my knowledge.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adriano•42,870
    @AdrianoEscarabote
    Posted over 2 years ago

    Hi Saravana Kumar, how are you? Welcome to the front-end mentor community! I really liked the result of your project, but I have some tips that I think you will enjoy:

    A good practice to center content is using grid or flex-box, avoid using margin or padding to make placements, use only in the latter case! we can do it like this:

    Flex-box:

    body {
        display: flex;
        align-items: center;
        justify-content: center;
        flex-direction: column;
        min height: 100vh;
    }
    

    GRID

    body {
        display: grid;
        min height: 100vh;
        place-content: center;
    }
    

    To improve the code structure wrap this div:

    <div class="attribution">

    with the semantic tag footer

    The rest is great!

    I hope it helps... 👍

    Marked as helpful
  • Divine Obeten•2,415
    @Deevyn9
    Posted over 2 years ago

    Hi Saravana, congrats on completing this project, your solution looks really great. Although I found the following issues:

    • The calculation for the Tip and Total amounts aren't accurate.
    • The Error messages don't clear out when the reset function is triggered.
    • The container isn't centered vertically, this can be fixed using body { display: grid; place-items: center; }
    • I also noticed that you didn't use the design for the mobile view and it makes it hard to use on small screens.

    If you have issues trying to fix these issues, you can use my solution

    I hope you find this helpful.

    Happy Coding! 🎉

    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
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