Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Password generator made in vanilla JavaScript

bem, sass/scss
P
Alexander3717•310
@Alexander3717
A solution to the Password generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am happy with how I made the custom slider — its thumb moves smoothly but the displayed value is always an integer. It also has magnetic endpoints: if you move the thumb near the start or end of the track, it will snap to the edge.

And if you decide to control the slider with keyboard, its step changes from any to 1 to ensure good UX.

What challenges did you encounter, and how did you overcome them?

I wanted to apply hover effects only on buttons that weren't disabled. This selector achieved that:

button:hover:not(:disabled) {}

I also wanted to apply hover effects only on devices that support hover. You can do that by putting all of your hover rules inside this media query:

@media (hover: hover) {}

After clicking the copy button, I wanted the "COPIED" text to appear instantly and then fade out after a short time. So I needed its opacity to go from 0 to 1 without transition but from 1 to 0 with transition. Here's how I did that:

span { // the "COPIED" text

    // other properties here

    --opacity: 0;
    --transition: none;

    opacity: var(--opacity);
    transition: var(--transition);
}
copyButton.addEventListener("click", (e) => {
    navigator.clipboard.writeText(passwordOutput.value)
    .then(() => {
        e.target.disabled = true;
        // I wanted opacity to transition only when going from 1 to 0
        // this achieves that
        copyMessage.style.setProperty("--transition", "none");
        copyMessage.style.setProperty("--opacity", 1);
        copyMessage.setAttribute("aria-hidden", "false");
        setTimeout(() => {
            copyMessage.style.setProperty("--transition", "opacity 0.2s");
            copyMessage.style.setProperty("--opacity", 0);
            copyMessage.setAttribute("aria-hidden", "true");
            e.target.disabled = false;
        }, 1500);
    })
});

On small mobile screens, the "TOO WEAK!" strength text was too wide to fit its div. Also, if you generated a long password and clicked the copy button, the "COPIED" text would overlap the password. I decided to address this by making a media query for small screens, where I removed the strength text (kept just the visual indicator) and removed the "COPIED" message completely.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Alexander3717'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

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.