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

CSS, HTML and not-that-well-working JavaScript

P
Katrien Schuermans•1,420
@katrien-s
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'm just completely lost in the javascript-form validation. And I have no idea how to clear the input. I've tried .reset(), I tried resetting the values with (something similar to) email[0].value = ''. Would anyone know a good source for more information? I tried a zillion YouTube-video's, but noone resets the value and I think that is why I'm running into errors?

As for the css & html: this was fairly logic and no questions here really.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • James Mitchell•295
    @iamjmitch
    Posted over 4 years ago

    Hi there,

    Ill do my best to try and explain some stuff

    To answer your reset question, try form.reset(). this worked for me.

    the other issue you are having is that the JS is not actually capturing the value of the input. const email = document.getElementById('email').value.trim() is running at page load, not when you hit the notify button so the inputted email address is never actually being captured and passed to the checkInputs() function for validation. Try declaring email on load const email = document.getElementById('email') and then inside your eventListener have something that looks like

    form.addEventListener('submit', (e) => {
      e.preventDefault();
     var inputtedValue = email.value.trim();
      checkInputs(inputtedValue);
    })
    

    this will make sure that the most up to date value is always passed to your check function when the user hits the notify button

    Then with your actual check function, if(!email) is checking to see if the variable doesn't exist which, as you are declaring it on page load, email will never not exist and the first block of code will never run. What you want to do is check whether that value is an empty string or ""

      function checkInputs(inputtedValue) {
      if (inputtedValue  === "") {
        message.classList.remove('valid')
        message.classList.add('invalid')
        message.innerText = 'You forgot to enter your address'
        message.style.display = 'inline-block'
      } else if (inputtedValue.match(emailPattern)) {
        message.classList.add('valid')
        message.classList.remove('invalid')
        message.innerText = 'Your email address is valid'
        message.style.display = 'inline-block'
      } else {
        message.classList.remove('valid')
        message.classList.add('invalid')
        message.innerText = 'Oops, something went wrong'
        message.style.display = 'inline-block'
      }
    }
    
    

    Have a look at the above modified function and see if you can work out whats going on. All the above put together should result in the functionality that your after. Hopefully this somewhat explains some stuff. Please let me know if you still dont understand and I can see how I can help

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hey there, Katrien S! 👋

    It's great to see you complete another challenge! 😀 Good work on this one! 🙌 Your solution looks good and is responsive! 👍

    I noticed that when the input element is focused, the rest of the content below the input element "jumps" down a bit due to the 2px border being added to the input element (which slightly increases its height and width). You can get rid of that and make the focused state appear more smoothly by adding an invisible 2px border to the input element (by setting the border-color to transparent) and simply changing the color of the border to a blue color when the input element is focused. 😉

    Keep coding (and happy coding, too)! 😁

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub