-
-
Notifications
You must be signed in to change notification settings - Fork 732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SplitDateTimeField doesn't show errors #1065
Comments
Yes, this is related to existing issue with multifields with this template pack. There is a tentative patch for this but I'm fairly sure that is the wrong way to fix it. #976 Any other ideas welcomed. |
simplylizz@3c84035 - I'm going to stick with this workaround, for my case (building a prototype) it's enough. Yes, it will highlight all Also I don't know if it will break any other use cases, I'm not a frontend guy. |
For anyone looking for a quick, unintrusive workaround, you can simply add
The container is only rendered if there's an error, so it wouldn't override anything unexpected. |
Description:
SplitDateTimeField
doesn't show errors. E.g. when only date is filled and time input is empty.The issue is in CSS, block with error has
display: none
property while other fields with error don't because they have an additional class.is-invalid
. See an attached screenshot.The text was updated successfully, but these errors were encountered: