Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

HTML CSS form

niranjan•120
@niranjan-inofty
A solution to the Intro component with sign-up form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Please provide feedback on JS form validation

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Dave•5,295
    @dwhenson
    Posted over 3 years ago

    Hey @niranjan-inofty - nice job here! 🙌.

    Here's some feedback you might like to consider:

    • I'd suggest centring the content on the page for this kind of component challenge. I do this by setting a min-height: 100vh and display: grid combined with place-items: center on the body. You can use flex as an alternative to grid if you prefer.
    • Regarding your JS, rather than adding an onclick in your HTML I would suggest using an eventListener in your JS - this is more flexible, and generally a better approach.
    • One other general point, I would suggest adding the novalidate attribute to your form using JS. This way we can use your custom validation if JS loads, and the browser if it doesn't.
    • I would suggest using the generic querySelector method rather than the more specific get by id, classname, name etc. Names and class names can change - I try to use a data attribute as the basis for my JS hooks as this avoids confusion. Here's a nice article on that: https://gomakethings.com/strategies-for-working-with-data-attributes-in-vanilla-javascript/
    • For your isEmptyOrSpaces function you could probably just use trim() on the value to remove whitespace and check if the value is true or false (an empty string is falsy)
    • I like that you have included a separate validation for email, and it seems to work well, which is great.

    My overall advice here is that the code is a bit repetitive, and looks like it could break quite easily! (But it works – so good job!! Everything else is extra.) If you wanted to improve things, I would suggest having a read about event listeners and event delegation.

    I think this approach would be better overall. I've put this challenge on my list to have another go at as I need to redo it!

    Cheers 👋

    Dave

    Marked as helpful
  • IRVINE MESA•1,835
    @DrMESAZIM
    Posted over 3 years ago

    @niranjan-inofty this is a perfect .Great work indeed

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