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

Responsive Signup Form

sass/scss
Kamasah-Dickson•5,570
@Kamasah-Dickson
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


Hello please anybody there? I have enabled a required attribute on the input element but it seems its not working . Please I need your help and your opinion.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • nanc•940
    @naiiiden
    Posted over 3 years ago

    I was struggling with this challenge for 2 days until I was playing around with my code... I removed the "required" attribute from the <input> tag and my JS worked. For unknown reason this interferes with JS :thinking:

  • Aakash Verma•9,500
    @skyv26
    Posted over 3 years ago

    Hello! Kamasah, I checked you work and I have noticed some issues.

    1. Never fix your footer with absolute or fixed property unless it is necessary. Your design is responsive but as move below 375px screen then you main heading/title moves outside the
      scope.

    2. You have use form elements inappropriately, because of that your form validation is not working. Please go throught your work again try to understand what you have done. **Hint: check your form submit button TYPE **

    3. I have question why you used inbuilt form validation, because in this challenge you had to implement custom form validation. So i would say stick with requirements. It is really important. Suppose any random client of you, give some work and he/she have some dedicated requirement then you can't give him work of your own choice. (I hope you understand what I am meant to say)

    Best of luck

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