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

Base Apparel coming soon page with HTML, Sass, and JavaScript

Riyana Gueco•495
@rngueco
A solution to the Base Apparel coming soon page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey!

I wasn't too sure what to put in the JavaScript validation side of this project, but I removed the required attribute for the email input element to prevent the :invalid styles from firing right at the start and did that check on the JavaScript side instead.

Aside from that, a simple pattern matching using the regex seen from MDN's docs.

I consider myself a JavaScript newbie, so please advise or give feedback. 🙏

Thanks!

Update: I have updated my solution based on feedback. The email field is now required, but the error message will not fire unless the user has focused and then removed focus on the field. Additionally, validity is now being checked before form submission, returning the appropriate error message based on whether the email input is empty or invalid. In case of user bypassing the required field and submitting an empty input anyway, an extra validation step is still checked on form submit.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Corvida Raven•680
    @SheGeeks
    Posted almost 4 years ago

    Hi Riyana! Great work on this challenge.

    For empty :invalid inputs, you may want to look into combining :invalid with another psuedo-class. This article is a helpful reference for accomplishing this: https://www.stefanjudis.com/notes/target-non-empty-but-invalid-input-element-with-css/

    Also want to note that I don't see a mobile image when viewing your work from my phone. Shows on desktop just fine.

    Marked as helpful
  • Jimmy Sweeney•350
    @sweenejp
    Posted almost 4 years ago

    Nice design! You really matched the solution well.

    I took a little different approach to the validation. I left on the required attribute because I think this keeps the error message from showing up until the user hits the submit button. Then I added an eventlistener with an event type of "invalid". Got help with this from this blog post here: https://daverupert.com/2017/11/happier-html5-forms/

    You can check out my solution here if you'd like: https://github.com/sweenejp/base-apparel-coming-soon-page

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

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