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

Interactive card details form solution || Responsive || Mobile first

accessibility
ROCKY BARUA•1,090
@Drougnov
A solution to the Interactive card details form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I've repeated a lot of codes in JavaScript. Is it okay for this challenge? If not how can I improve my code?

The form is getting submitted with just only CVC input. How can I fix it so that the form checks all the inputs validation first, then show the modal?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted almost 3 years ago

    for your JavaScript code some of your codes are repeated but is not a lot My Recommendation for the inputs.forEach(() => {}) => create a functions per nested conditions so it will decrease the logical thinking what I mean about that is it will became more easier to read your code if you do this... example

    const containsNameInput = function (input) {
     if(input.value === ''){
                    input.parentElement.classList.add('error-empty');
                    input.parentElement.classList.remove('error-invalid');
                }else if(input.value !== '' && input.value.match(/^[0-9]+$/) !== null){
                    input.parentElement.classList.remove('error-empty');
                    input.parentElement.classList.add('error-invalid');
                }
                else{
                    input.parentElement.classList.remove('error-empty');
                    input.parentElement.classList.remove('error-invalid');
                }
    // add this function to the parent condition statement
    // So on and so fort for the others are nested condition
    }
    

    for the second question: "Modal"

    much better used this kind of way instead to loop the forms so it will check each input once the user click the submit button ("submit" handler)

    // their variables contains the value of their inputs
    const nameInput = document.querySelector(".name-input").value;
    const numberInput = document.querySelector(".name-input").value.length;
    const monthInput =  document.querySelector(".month-input").value;
    const yearInput = document.querySelector(".year-input").value;
    const cvcInput = document.querySelector(".cvc-input").value.length;
    
    // second operand of condition is not 100% accurate is just an example
     if(nameInput === 'name' &&
         numberInput === 16    &&
         monthInput === "month" &&
         yearInput === "year" &&
         cvcInput === 4) {
             modal.style.display = 'flex or block";  
    }  else {
     // you can create a code here if you want to throw an error
     // in the webpage
    }
    
    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 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