Description
The registration page (register.ftl) uses raw HTML for its submit button instead of the shared buttons.ftl macros used by the login page and other forms. This results in inconsistent button styling, spacing, and wrapper markup. The register button also references an undefined kcButtonLargeClass property and lacks the kcFormActionGroupClass wrapper that provides consistent top padding.
Value Proposition
A single button macro ensures consistent look and feel across all login theme pages. Changes to button styling or spacing only need to happen in one place.
Goals
- Refactor
register.ftl to use @buttons.actionGroup and @buttons.button macros for both the regular and recaptcha submit buttons
- Remove the unused
kcButtonLargeClass references from the register form
Non-Goals
- Refactoring buttons in other themes (e.g. base theme)
- Changing the visual appearance of existing buttons
- Unifying buttons across all login pages beyond register (can be done incrementally)
Discussion
No response
Notes
No response
Description
The registration page (
register.ftl) uses raw HTML for its submit button instead of the sharedbuttons.ftlmacros used by the login page and other forms. This results in inconsistent button styling, spacing, and wrapper markup. The register button also references an undefinedkcButtonLargeClassproperty and lacks thekcFormActionGroupClasswrapper that provides consistent top padding.Value Proposition
A single button macro ensures consistent look and feel across all login theme pages. Changes to button styling or spacing only need to happen in one place.
Goals
register.ftlto use@buttons.actionGroupand@buttons.buttonmacros for both the regular and recaptcha submit buttonskcButtonLargeClassreferences from the register formNon-Goals
Discussion
No response
Notes
No response