Skip to content
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

[Bug]: DatePicker doesn't show error message #5500

Closed
panmona opened this issue May 8, 2024 · 2 comments
Closed

[Bug]: DatePicker doesn't show error message #5500

panmona opened this issue May 8, 2024 · 2 comments
Assignees
Labels
Type: Bug 🐞 Something isn't working
Milestone

Comments

@panmona
Copy link
Contributor

panmona commented May 8, 2024

Blazorise Version

latest version that is on branch rel-1.5

What Blazorise provider are you running on?

Material

Link to minimal reproduction or a simple code snippet

Use the ValidationsPage.razor in the project Blazorise.Demo.
Change the usages of DateEdit to DatePicker.

Steps to reproduce

  • Start the Blazorise.Demo project
  • Go to the Validations page
  • Make the DatePicker validation trigger

What is expected?

  • The validation error message is shown
  • The field is red

What is actually happening?

  • No validation error message is visibly shown
    • but the message exists in the DOM tree. Display hidden is applied to it.
  • The field is red

image

What browsers do you see the problem on?

Chrome

Any additional comments?

This seems to have been reported in the past e.g. #5121, #5433, #5445, but the message is also not shown on the latest version that is on rel-1.5 branch.
It seems to occur because the input element with the classes "form-control is-invalid" has the flatpickr-wrapper div around it. Therefore the Material CSS rule which makes the invalid-feedback visible, doesn't apply.

Is there possibly also any workaround to this?

@panmona panmona added the Type: Bug 🐞 Something isn't working label May 8, 2024
@stsrki
Copy link
Collaborator

stsrki commented May 9, 2024

We need to see what is different for the Material provider.

In the meantime, can you try clearing the cache and see if it helps?

@stsrki stsrki self-assigned this May 9, 2024
@stsrki stsrki added this to the 1.5 support milestone May 9, 2024
@stsrki stsrki closed this as completed May 9, 2024
@panmona
Copy link
Contributor Author

panmona commented May 14, 2024

Thanks for the fix.

@stsrki stsrki added this to Support Aug 3, 2024
@stsrki stsrki moved this to ✔ Done in Support Aug 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug 🐞 Something isn't working
Projects
Archived in project
Development

No branches or pull requests

2 participants