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

Interactive card details form build with Html, Sass, Vanilla Js

suhayb jirde•1,110
@suhaybjirde
A solution to the Interactive card details form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Daniel Dekany•920
    @dknyd
    Posted over 2 years ago

    Hey Mate,

    Great solution!

    I just finished the same challenge but had difficulties with the error messages after one incorrect completion.

    What I mean is for example when user inputs wrong data type (like numbers in name field), and he corrects it, the error message should disappear and the border of the field should change back to default color i/o red.

    I see you solved that part in a way that as soon as the user starts to type in the field with the red border and visible error message, the error message instantly fades and the border changes back to default, great one!

    Also I just now see that the validation is continuous after every input typed (mine only validates the whole form after pressing confirm), did you do that with an event listener?

    One thing I noticed - when I want to submit with any input field blaNk, error message says "Can't be blaCk". :)

    Keep up the good work!

    Daniel

    Marked as helpful
  • suhayb jirde•1,110
    @suhaybjirde
    Posted over 2 years ago

    thanks pro yes i'm using 'keydown' event and data attribute to toggle that but i wrote a lot of unnecessary code i saw some guys did it like that with just 70 line of code and also i couldn't do the spacing when you try to write the card number there should be a space between every four digits but i'm still working on it you also did great pro you can also read my code to see how i did it

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