[BUG] Trezu - Create Treasury: Validation message persists after correcting input

[rknearn-qa]

Summary

On the Create Treasury page, when a user enters invalid input in the Treasury Name field (e.g., exceeding maximum length), a validation error is displayed. After correcting the input to meet validation requirements, the validation message remains visible, indicating that the error state is not cleared properly.

Preconditions:

• User connected to Trezu (maledress6270.near)

Steps To Reproduce

1. Open Create Treasury page
2. Enter invalid symbols or exceed maximum allowed length in the Treasury Name field
3. Modify the input to satisfy validation rules (e.g., reduce character count within allowed limit)

Actual Result:

• Validation error message remains visible
• Field appears corrected but still shows validation error state

Expected Result:

• Validation message should automatically disappear once input meets all validation criteria
• Field error state should be cleared immediately or on blur/re-validation trigger

Special Notes:

Possible Root Cause:

* Validation state may be triggered only on `onSubmit` or `onBlur` and not re-evaluated on `onChange`.
* Error state may not be reset properly in form state management (e.g., stale validation flag in form controller).

Workarounds:

• Refreshing the page clears the validation state

Repro Rate:

Always

Setup - OS - Browser - Environment

• OS / Devices: Windows 11 (x64), Motorola G23 (Android 14), Iphone XR (iOs)
• Screen resolution(s): 1366 x 768, 1600 x 720, 1792×828
• Browser(s) + version(s): Chrome (144.0.7559.97), Mozilla Firefox (147.0.2), Brave (1.86.148)
• Wallet: Meteor
• App environment: Staging (trezu.app)
• Near Network: Mainnet

Resources & Additional Notes

Impact:

User Impact:

• Users may believe the input is still invalid even after correction
• Confusion during treasury creation process

System Impact:

• Frontend validation state inconsistency

Business / Release Risk:

• Minor UX degradation in a core creation flow
• Potential friction during onboarding

QA Verdict:

Verdict: ❌ Needs Fix
Rationale:

• Validation behavior must be reactive and accurate to prevent UX confusion
• Does not block system functionality but degrades user experience

Recommendation:

• Ensure validation re-triggers on input change
• Reset error state when validation conditions are satisfied
• Add UI test case for dynamic validation clearing behavior

Priority

🟢 P3 : Normal