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

Newsletter signup form

bootstrap
Tom Roche•330
@TomrocheDev
A solution to the Newsletter sign-up form with success message challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I haven't got much experience with form validation, so the validation was sort of a challenge for me. I struggled with the error message because the :invalid pseudo selector gave the error message when the user was typing in the email address. That was not the experience I wanted to create so I fixed the problem with JavaScript. I'm not sure if this is the correct way to handle form validation, so any advice is welcome.

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

Correct ways of form validation.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex•3,130
    @Alex-Archer-I
    Posted about 1 year ago

    Hi!

    There are a few ways to validate input field via JS. For example, you can check the value every time when it's changing with the input event. This event triggers every time user types something, but that is not a very popular method cos it's could be annoying to get error message before you write all what you want.

    Alternative way is to use change or focusout events. Those events both triggers when input loose focus, but change works only if it's value were changed.

    Than you need to validate input's value. The easiest way to do it by using regular expressions. For now I use this one - /[-.\w]+@([\w-]+\.)+[-\w]/g, but I need to improve it cos it's not validate numbers.

    Also I recommend you to learn about special JS object FormData and use it to collect data from forms. This object is quite useful when you need to send data to the server, so It is a good habit for the future projects.

    Oh, and I was recently wondered about accessibility issues which occurs when we are using custom error messages and I found this article.

    I hope something of this could be helpful =)

    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

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