-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
web: Indicate when caps-lock is active during password input. #12733
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for authentik-docs canceled.
|
✅ Deploy Preview for authentik-storybook ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
2588d77
to
3d7a451
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #12733 +/- ##
==========================================
+ Coverage 92.68% 92.76% +0.08%
==========================================
Files 785 785
Lines 39623 39623
==========================================
+ Hits 36724 36757 +33
+ Misses 2899 2866 -33
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the show caps lock
is a bit over-engineered; I gave a more lit-like suggestion.
3d7a451
to
753827f
Compare
4c6f199
to
ae9b6ca
Compare
Determining the state of the caps-lock key can be tricky as we're dependant on a user-provided input to set a value. Thus, our initial state defaults to not display any warning until the first keystroke. - Revise to better use lit-html.
ae9b6ca
to
be69786
Compare
Details
Hey team! 👋
I had fun implementing the caps-lock detection feature! Since we rely on keystroke events to determine the caps-lock state, the warning stays hidden until we get that first user input.
This is my first time contributing to the lit-html parts of our codebase, and I'm excited to get your thoughts. I was able to bring the
InputPassword
component up to speed with some of authentik's more recent component design patterns, such as leaning on the Lit's ref directive to manage event listeners.I'd love feedback on my approach to both the LitHTML patterns and authentik's existing conventions.
Looking forward to your review!
Checklist
ak test authentik/
)make lint-fix
)If an API change has been made
make gen-build
)If changes to the frontend have been made
make web
)If applicable
make website
)