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

Responsive Contact Form using HTML, CSS, & JavaScript

Rebecca Padgett•2,100
@bccpadge
A solution to the Contact form 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 added valid/error icons for first/last names and email input fields, and darkened the error icons/messages for better contrast.

The icons I used are from Font Awesome

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

N/A

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

N/A

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•9,390
    @MarziaJalili
    Posted 6 months ago

    Awesome work, buddy!

    Some areas you can amend:

    • First, the message box somehow resizes the page. If you want to get rid of it you can use the position property.

    Since it positioned according to the page, you don't need to set the position: relative; on any other element for relative positioning. Just have to use absolute positioning on the box itself.

    This is how you set the property:

    .message-box {
      position: absolute;
      top: 5%;
      left: 50%; /* to center it */
      z-index: 10; /* to make it appear on the top of the form */
    }
    
    • Second, when the user tries again to provide valid data, the error states are still there. It would be better if you got rid of them using the onChange on the inputs for a more user friendly layout.

    This is how you can set the event listener for it:

    input.addEventListener('input', function() {
        console.log("error state removed!")
        // some conditions to remove the error states 
        // according to your code
    });
    

    This will log "error state removed!" to the console every time the user types into the email field. And, by having those condition, it will remove the error states, too.

    Overall, the solution is flawless!

    Keep up on building master pieces like this one!

    😎😎😎

    Marked as helpful
  • Marzia Jalili•9,390
    @MarziaJalili
    Posted 4 months ago

    A tiny suggestion:

    I am kinda planning to create a study group on Google Chats let me know if you're interensted to be added there. Let's beat Elon Musk together.

    😂😂😂

  • MEHNOOR SHAHBAZ•720
    @Mahnoor366880
    Posted 5 months ago

    This comment was deleted 5 months ago

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