Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

contact form validation Html/css/JS

Guilherme Fernandes Vidotti•520
@Vidottizzz
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 completed the validation of the form, and then when every input are filled, the alert show a message saying that it is completed, but i used the preventDefault to prevent the form being submited, and i dont know how can i stop the preventDefault from working after the inputs are completed, so the form isnt sending nothing, can someone help me ?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grego•1,430
    @Grego14
    Posted about 1 year ago

    👋 Hello! 🎉 Congratulations on completing the challenge! 🎉

    The preventDefault() method is used in a form when you don't want it to be sent, in this case you want it to be sent when everything is correct.

    To prevent the form from being submitted when there is an error, you can use the preventDefault() along with validations, something like this:

      nameValidate();
      lastNameValidate();
      emailValidate();
      radioValidate();
      checkBoxValidate();
    
    if (!(checkBox.checked === true) && 
    !(fields.value.length > 0) && 
    !(fields.value.length > 0) && 
    !(emailRegex.test(fields.value)) && 
    !(htmlRadio1.checked || cssRadio2.checked)) { 
      return e.preventDefault()
    }
    
      alert("Message Sent. Thanks for completing the form. We'll be in touch soon!");
    

    Here we would be using all the validation functions before verifying that the form is correct, since those functions remove and add the errors.

    And we use return e.preventDefault() in validating whether the inputs are invalid to prevent the alert from being sent.

    Using the tag br is considered a bad practice, as it should be used only when breaking the line is necessary, such as a poem of a few lines. It's best to use styles to achieve what you want.

    When using multiple inputs in a container, it's best to use the 👉 Fieldset tag instead of a div.

    You have duplicated ids in two input elements lname.

    No need to use the type attribute in the script tag

    I hope this helps! 😁

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