This is caused by the text field template being overridden for the front-end in a CWP module. The way the template is overridden, there's not much we can do to fix the actual functionality in that scenario without adding some hard coupling between PasswordField and ConfirmedPasswordField classes - which isn't really patch release friendly.
This PR changes the test to validate just that it works in the CMS with default templates - it makes no promises about the functionality working on the front-end.
[x] All commits are relevant to the purpose of the PR (e.g. no debug statements, unrelated refactoring, or arbitrary linting)
Small amounts of additional linting are usually okay, but if it makes it hard to concentrate on the relevant changes, ask for the unrelated changes to be reverted, and submitted as a separate PR.
Description
Fixes https://github.com/silverstripe/recipe-kitchen-sink/actions/runs/7572648719/job/20622988035
This is caused by the text field template being overridden for the front-end in a CWP module. The way the template is overridden, there's not much we can do to fix the actual functionality in that scenario without adding some hard coupling between
PasswordFieldandConfirmedPasswordFieldclasses - which isn't really patch release friendly.This PR changes the test to validate just that it works in the CMS with default templates - it makes no promises about the functionality working on the front-end.
Issues
Pull request checklist