Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 5 months ago

password generator app

P
toshirokubota•1,340
@toshirokubota
A solution to the Password generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I had various issues on customizing the input range bar and its thumb. I overcame by consulting on google and AIs. I still have not been able to control the thumb programmatically, as its location may misalign when the page is refreshed.

I generated a password simply by choosing characters randomly from the pool. There is no guarantee that it does include a number when the 'Include Numbers' check box is checked. What is does is simply to add 0-9 into the pool of characters.

What specific areas of your project would you like help with?

I would like to know how to move the thumb of a range input programmatically, so that I could fix the misalignment issue mentioned above.

In addition, any suggestions on html/css/script for improvement are appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mikhil Desai•640
    @mike15395
    Posted 5 months ago

    Congratulations @toshirokubota on completing the challenge!

    Here are few pointers which will improve your solution:

    1. Styling input slider

    i have used character-length-input as id for my input , you change accordingly to your code

    CSS part

    #character-length-input {
        -webkit-appearance: none;
        appearance: none;
        width: 100%;
        height: 6px;
        background: linear-gradient(to right, var(--neon-green) 50%, #18161F 50%);
        /* border-radius: 5px; */
        outline: none;
        cursor: pointer;
        border: none;
      }
      
      /* WebKit browsers (Chrome, Safari) */
      #character-length-input::-webkit-slider-thumb {
        -webkit-appearance: none;
        appearance: none;
        width: 24px;
        height: 24px;
        background: #E7E7E7;
        border-radius: 50%;
        cursor: pointer;
        box-shadow: 0 0 3px rgba(0, 0, 0, 0.3);
      }
      
      #character-length-input::-webkit-slider-thumb:hover {
        background: var(--dark-grey); /* Dark grey */
        border: 2px solid var(--neon-green);
      }
    
    

    JS part for adjusting percentage on change

    characterInput.addEventListener("input", function () {
      document.getElementById("character-length-value").innerHTML =
        characterInput.value;
    
      const min = this.min;
      const max = this.max;
      const value = this.value;
      const percentage = ((value - min) / (max - min)) * 100;
    
      // Dynamically update the background gradient
      this.style.background = `linear-gradient(to right, #A4FFAF ${percentage}%, #18161F ${percentage}%)`;
    });
    
    1. you missed COPIED text after clicking on copy button
    2. check font color of heading and strength word as per design
    3. add hover effect on generate button and remove border as per design

    Rest your code is well written and maintained! Happy Coding!!

    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