IBX-11959: Added password requirements info to Set new password screen - #2014
Open
tischsoic wants to merge 3 commits into
Open
IBX-11959: Added password requirements info to Set new password screen#2014tischsoic wants to merge 3 commits into
tischsoic wants to merge 3 commits into
Conversation
Co-Authored-By: Claude <noreply@anthropic.com>
…s template Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
|
alekmick
approved these changes
Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Related PRs:
Description:
Frontend of the "Set new password" screen. The configured password requirements are listed above the password fields from the data exposed by ibexa/user#132 (
ibexa_password_requirements(content_type)), and after a failed submit the requirements that passed are marked with a green check while the backend's own validation messages render under the failing field. No live validation — the state is recomputed server-side on each submit.All user-facing strings come from backend translations; the only new key is the intro sentence.
Two spacing rules in
_login.scssapply to every account screen (login, forgot password, …), both to match the design: a tighter headline line-height and a smaller top margin on form-error rows.On a passwords-mismatch submit the requirement list stays unmarked: the password constraint doesn't run while the repeated field is out of sync, so met/unmet is genuinely unknown (the design's "all green + passwords don't match" state isn't reachable server-side).
Without ibexa/user#132 the screen renders exactly as before, so this can be reviewed independently.
For QA:
abcin both fields — one error per unmet rule under New password, met rules get a green check.Documentation: