Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 6 months ago

Mortgage Calculator

react
Julianna Messineo•290
@mathematiCode
A solution to the Mortgage repayment calculator challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm proud of figuring out how to manage the various states for each input like each one having it's own 'status' and then the overall form having it's own status. Next time I'd like to reduce duplicate code and create re-usable components, such as an input component.

What challenges did you encounter, and how did you overcome them?

How to put the units inside of the inputs and now throw off the rest of my formatting.

What specific areas of your project would you like help with?

If I really needed to use an effect to trigger a submission of the form when the user submits it and then changes something or if there's a way to do it without an effect. But also, any feedback is appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jay Khatri•4,230
    @khatri2002
    Posted 6 months ago

    Hi! The developed solution looks great! Just one minor suggestion to improve the user experience:

    Fixing Layout Shift on Input Focus

    When focusing on the input elements, a slight layout shift occurs, which becomes noticeable when you type a value and then toggle focus on the input.

    Why Layout Shift Happens:

    This is due to the addition of the border property on focus. Initially, there is no border, but once focus occurs, a 2px solid border is added, which causes the content to shift.

    .amount-container:focus-within > input,
    .interest-container:focus-within > input,
    .term-container:focus-within > select {
      outline: none;
      border: solid var(--lime-500) 2px; /* Causes layout shift */
    }
    

    To prevent this layout shift, always provide a 2px border but set it to transparent initially. When the input is focused, change only the color of the border. This avoids any shift in layout while achieving the same visual effect.

    /* Default state */
    .amount-container > input,
    .interest-container > input,
    .term-container > select {
      border: solid transparent 2px; /* Set border initially */
    }
    
    /* Focus state */
    .amount-container:focus-within > input,
    .interest-container:focus-within > input,
    .term-container:focus-within > select {
      outline: none;
      border-color: var(--lime-500); /* Change color on focus */
    }
    

    Alternative Approach: Outline

    Alternatively, consider using the outline property instead of the border, which won’t affect the element’s size or cause any layout shifts.


    Great work so far! Keep up the excellent progress and attention to detail! 🚀

    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