Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

Mail validation using event listener

Sanjeet Rai•100
@Sanjeet204
A solution to the Ping single column coming soon page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I was quite addictive of using position to relocate elements to their perfect location however, this time taken a challenge to use less position and manage to perform to task beautifully using margin and padding instead of position.

In terms of interactivity it was quite easy only needed to validate email. Please share your views regarding this challenge .

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted about 2 years ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have other recommendations regarding your code that I believe will be of great interest to you.

    JAVASCRIPT 🟡:

    • The way you declared variables are need to be well structured and organized

    • Take a look at the following example code which describes a better way of declaring variables to have a well structured code
    const firstName = "Your";
    const lastName = "Name";
    const emailAddress = "example@some.com";
    const password = "supersecret";
    
    • instead try this,
    const firstName =  "Your",
           lastName =  "Name",
           emailAddress = "example@some.com"
           •••                
           •••         // n number of declarations
           password = "supersecret";   // make sure to add a semicolon at end of last declaration
    
    • This single line declaration with separated commas will helps you to have a better structured code and improves readability though

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

    Marked as helpful
  • Josh•1,120
    @josh76543210
    Posted about 2 years ago

    Hello @Sanjeet204,

    Congratulations on completing the challenge!

    Here is another suggestion to improve the look of your page:

    Center the social media icons inside their respective divs using flexbox instead of padding. The divs are already displayed as flex so all you have to do is add align-items and justify-content. These can be used to center the flex-items (in this case the icons) vertically and horizontally.

    Just add them to your divs like this:

    .icons > div {
      align-items: center;
      justify-content: center;
    }
    

    And then remove the padding:

    .icons > div {
      padding-top: 11px;
      padding-left: 11px;
    }
    

    Your icons should now be perfectly centered inside your divs.

    Hope this is useful. Happy coding!

    Marked as helpful
  • Shivraj K•400
    @Shivraj-K09
    Posted about 2 years ago
    • Great job! It's good to see that you were able to achieve the desired layout using margin and padding instead of relying solely on positioning.
    • One suggestion I would make is to use const instead of let when declaring pattern since the variable doesn't need to be reassigned. It's a small change, but it can help communicate to future readers of the code that the variable is intended to be constant.

    Keep up the good work! 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

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