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

Responsive sign up form with flex, grid and javascript

Tomás Arrativel•200
@Tomas-Arrativel
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


I have some problems with the positioning of the error icon, if you could help me I would appreciate it. if you can, give me your recommendations. thanks

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted over 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 an efficient way of declaring variables
    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
  • vinu cyril•980
    @vinuman
    Posted over 2 years ago

    Hello,

    Good job completing the project.

    • You can make the position for the form as relative and give an absolute position for the error icon.

    • You can then use the top, right and transform property to have it where you want. For example, i have used the following for the first error sign(the one for the first name),

    .material-symbols-outlined{ position: absolute; top: 11%; right: 6rem; transform: translateY(-50%); color: #FF7979; display: none; }

    • Additionally, you can target the email input field to ensure that a correct email format is updated. This is the JS code i used, the error icon is the next element after the email input and the error message is the element after that. You can put this inside your button eventlistener.

    const emailRegex = /^[^\s@]+@[^\s@]+.[^\s@]+$/; if(!(emailInput.value.trim().match(emailRegex))){ const errorMessage = emailInput.nextElementSibling.nextElementSibling; errorMessage.style.display = 'block'; const errorIcon = emailInput.nextElementSibling; errorIcon.style.display = 'block'; }

    • Finally you can remove the default outline for the input fields with the following CSS code,

    input:focus{ outline: 1px solid #5E54A4; }

    • Hope this helps, 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