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

11st challenge: Ping coming soon page

drunken_neoguri•290
@DrunkenNeoguri
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 wrote this using Google Translate. Please forgive the grammar.)

Hello!

This is the 11th challenge.

From this challenge, you will finally be able to use JavaScript! I started learning the basics of JavaScript a few days ago, so there are many things I don't know completely.

So this challenge was too difficult for me as I am new to JS.

Here are the things that were difficult while working this time:

  1. An error message is displayed when a blank or incorrect character is entered, but I want to press the message only once.

Is there any way to make the error message appear only once? And if I input a normal message, is there a way to clear the error message?

  1. I set the style.border value to change so that the color of the border of the input also changes when an error message is applied to the JS function, but it didn't work.

Is there any way to solve this?

It's my first challenge, but I'm glad I learned a little bit about how to read JS code through this work! There were many shortcomings, but I will continue to study hard!

Thank you for watching! > ▽<)/ If you have any other advice, please feel free to tell me!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Luka•820
    @LukaKobaidze
    Posted over 3 years ago

    Hello!

    In your outputmessage(self) function

    var message;
    
    message = document.createTextNode(self);
    errormsg.appendChild(message);
    

    you can remove these lines and instead of that, add errormsg.textContent = self. This will change the text of that element.

    The reason why border color is not applying is because in this line var address = document.querySelector('[name="email"]').value you are getting value of the element instead of the actual element (remove .value), and then add address.style.borderColor = 'any color'

    Marked as helpful
  • Abhik•4,820
    @abhik-b
    Posted over 3 years ago

    👋 Hello Drunken Neoguri , nice to see you complete another challenge with a great solution, well done 🤩🤩🤩

    If I have understood correctly your question then a easy solution is to add a change event listener to the email input & then check there if email matches then show error message else hide it. Another way to deal that is whenever the Notify Me button is clicked then check the & display/hide the error message. Here is the code for this approach (please change it according to your code):

    const emaiInput = document.querySelector("input");
    const emailChecker = /\S+@\S+\.\S+/;
    
    document.querySelector("button").addEventListener("click", () => {
      if (!emailChecker.test(emaiInput.value)) {
        emaiInput.classList.add("error");
    
        document.querySelector(".error-message").style.display = `block`;
        setTimeout(() => {
          document.querySelector(".error-message").style.transform = `scale(1)`;
        }, 100);
      } else {
        if (emaiInput.classList.contains("error")) {
          emaiInput.classList.remove("error");
          document.querySelector(".error-message").style.transform = `scale(0)`;
          setTimeout(() => {
            document.querySelector(".error-message").style.display = `none`;
          }, 300);
        }
      }
    });
    

    Hope this helps 🤞 and please code amazing solutions like this 👍

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