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

vanilla js for form validation

P
Claudia•320
@cla91
A solution to the Pod request access landing page 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?

Next time I would like to write a cleaner CSS and JavaScript. If there were more form fields, I would have created functions for adding and removing messagges to make the code a bit cleaner and manageable.

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

At the beginning I had used the invalid event, but after some test I found out that the browser email validation was a bit too lax so I couldn't use the invalid event anymore because it gets fired after the browser did the validation, so I went back to the good old submit event :')

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

I'd like feedback on the use of the background properties for double image and for the js

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•5,740
    @thisisharsh7
    Posted about 1 month ago

    Congrats on completing the challenge! Your background layering using background-blend-mode and custom email validation is well-executed!

    Some suggestions:

    1. When error/success messages appear, the layout height shifts slightly. To prevent that:

      • Reserve space below the form using a fixed min-height on the .message element.
      • Or always render the element with visibility: hidden to avoid reflow.
    2. For cleaner JS: Instead of repeating messageDiv.textContent = ... and classList.add/remove in many places, you can make a small function that shows the message. Then just call that function — it keeps code clean and short

    Overall a good work - 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

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