Input fields displayed „invalid“ (red border) without form submission

[bentuna]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

Form fields with validity check are marked :invalid right upon loading, without any form submission. It seems like an overall regression of the latest point release:

Steps to reproduce

1. Open the login page or another app that uses forms.

Expected behavior

Show :invalid style only after form submission when validity check failed.

Nextcloud Server version

29

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[susnux]

Context: The validation is only triggered by user input, so there must have been either user interaction or some JS is forcing a validation.

[tjareson]

Similar behaviour with nc 30. On google chrome and firefox. No user input made, just opened the url.

[GustavoSatig]

I am experiencing the same issue on NC 30. The problem occurs as soon as I open the URL.
I also noticed that this issue happens on the nextcloud demo as well.

[mitsol]

I have the same issue on MacOS 15.1.1 with Google Chrome and Safari.

[susnux]

If you encounter the same issue please use the 👍 reaction on the initial issue, we sort by that for seeing what community needs the most.

Otherwise please do not comment if you do not have new information that just annoys anyone that is subscribed to this issue ;)

I assigned a low tag as this is a confirmed issue, but only a light visual annoyance. Meaning it is not on our priority list, but of course anyone is very welcome to provide a pull request with a fix 💙