Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Password Generator

Johan•40
@Johanh0
A solution to the Password generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Password Generator

  • What did you find difficult while building the project?

CSS: I found some difficult styling the input range, specially having two different colors on the input.

JavaScript: I found some difficult when I try to create a function that check if all my checkbox inputs were unchecked or at least one were checked. Because depends on this the generate button would be able or not. Also I didn't know how copy with the clipboard, looking on internet I found an old way to do it (deprecated). I'll let the way below of how you copy a value on your clipboard just because I didn't know until this project and maybe can help somebody:

const myInput = document.querySelector("#my-input").value;
const submitBtn = document.querySelector("#submit");

function copyClipboard() {
    try {
        // This line copy what you have on your input.
        navigator.clipboard.writeText(myInput);
    } catch (err) {
        console.log("Error with the clipboard API", err);
    }
}

submitBtn.addEventListener("click", copyClipboard);
  • Which areas of your code are you unsure of?

I would say that the area of my code that I'm unsure is on the Strength level bars. They don't are really analyzing the password an making sure if is really a strong password or not. they're just checking how many checkboxes are marked and depends on this make a result.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Johan's solution.

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.