---
title: "Comment by Tiffany Spark on \"How to Fix Form Validation UX: Switching from :invalid to :user-invalid\" | Hashnode"
description: "this is such a small change but it makes such a difference to how a form feels — i honestly used to just live with the premature red borders and assume clients"
url: "https://hashnode.com/posts/how-to-fix-form-validation-ux-switching-from-invalid-to-user-invalid/699376d10c6be409a83e961f/comment/699499aeae5d02f7ab121d13"
---

[Discussion](https://hashnode.com/posts/how-to-fix-form-validation-ux-switching-from-invalid-to-user-invalid/699376d10c6be409a83e961f)

Comment [How to Fix Form Validation UX: Switching from :invalid to :user-invalid](https://hashnode.com/posts/how-to-fix-form-validation-ux-switching-from-invalid-to-user-invalid/699376d10c6be409a83e961f)

[Tiffany Spark](https://hashnode.com/@markupandmatcha)

[Feb 17](https://hashnode.com/posts/how-to-fix-form-validation-ux-switching-from-invalid-to-user-invalid/699376d10c6be409a83e961f/comment/699499aeae5d02f7ab121d13)

this is such a small change but it makes such a difference to how a form feels — i honestly used to just live with the premature red borders and assume clients would ignore it. bookmarking this to actually fix it properly on my next build. the browser support table is super helpful too, good to know it is basically safe to use now