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

form validation js

tortaruga•790
@tortaruga
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 are you most proud of, and what would you do differently next time?

I'm proud that I managed to finish it and that I didn't take as long as I thought I would, but I'm still not very good at judging sizes

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

i couldnt get the validation to work, because I had forgotten to add defer in the script tag; also the linear-gradient acts different on firefox and chrome: on firefox it's vertical instead of horizontal; i just changed the direction from 90deg to 180 and now it works fine on firefox too, but I'm not sure why

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

I used the flex property to style the form and the image, by giving both flex: 2, and I like the result, but I don't really understand how the property works. I just tried random values until it looked good

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Koda👹•3,830
    @kodan96
    Posted about 1 year ago

    hi there! 👋

    the flex property is short for flex-grow, flex-shrink and flex-basis:

    • flex-grow: Defines the ability for a flex item to grow if necessary. It accepts a unitless value that serves as a proportion. A value of 0 prevents the item from growing, while a value of 1 allows the item to grow and fill the container proportionally.

    • flex-shrink: Defines the ability for a flex item to shrink if necessary. It also accepts a unitless value that serves as a proportion. A value of 0 prevents the item from shrinking, while a value of 1 allows the item to shrink proportionally when necessary.

    • flex-basis: Defines the default size of an element before the remaining space is distributed according to the flex-grow and flex-shrink properties. It can be a length or auto.

    applying one value to flex will modify only the flex-grow property, the second will modify flex-shink, and the third is for flex-basis.

    Hope this was helpful 🙏

    Good luck and 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
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