contact form with tailwind

Solution retrospective
In the process of completing this form, I will try to find the best solution. In this process, I learned a lot.
What challenges did you encounter, and how did you overcome them?In the process of completing this form, I encountered two problems, which made me a little entangled. I don't have a good solution. Here are the problems I encountered and the solutions
-
The
input
tag is added withrequired
. At this time, the pseudo-class selector:invalid
will take effect directly during initialization, resulting in an error message being displayed as soon as the page is opened. I think this is not good.- Method 1: Add the
novalidate
attribute to the form, and then check it yourself through js. This is too troublesome. - Method 2: Use
:foucus + :invalid
to display the error message, which is only displayed when focused.
- Method 1: Add the
-
email
has two checksrequired
andtype=email
. Any failure in any check will make the pseudo-class:invalid
effective, and there is a requirement to check the email format in the requirements. So here I can only use js to distinguish the check type and modify the corresponding text.
For the above problems, if you have a better method, please let me know, thank you
Please log in to post a comment
Log in with GitHubCommunity feedback
- @younes-atyq
Hi, great job!
I recently watched Kevin's video addressing the same issue you encountered but in vanilla css.
I searched for that pseudo element in Tailwind CSS but couldn’t find it. If it hasn’t been added yet, you can always incorporate a custom CSS code into your project.
Additionally, it’s advisable to set a fixed height for your form elements. This way, when an error message appears, it won’t push the rest of the content down.
Marked as helpful
Join our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord