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

Component: Calendar - form control state mismatch on blur #13982

Closed
RafalSzczuka opened this issue Oct 30, 2023 · 1 comment
Closed

Component: Calendar - form control state mismatch on blur #13982

RafalSzczuka opened this issue Oct 30, 2023 · 1 comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@RafalSzczuka
Copy link

Describe the bug

Control should emit onBlur event AFTER is marked as touched. It's applied correctly for all other controls but not for Calendar for some reason.

I have a logic that I'm listening to onBlur event and after that creating dynamic error message below control. In the case of Calendar input is marked red, but the error message appears only after a second blur event occurs.
It's because this line should be moved after the model was marked as touched:
image

This is an example in inputNumber component:
image
Event emit is after the update model.

Environment

Windows + Chrome/Firefox

Reproducer

No response

Angular version

16.2.9

PrimeNG version

16.5.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.16.0

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

@RafalSzczuka RafalSzczuka added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Oct 30, 2023
Copy link

This issue has been automatically marked as stale due to a lack of activity. If this issue is still relevant to you, please leave a comment so we can keep it open. We apologize for not being able to prioritize it sooner. If you have any new information or questions, please share them in your comment!

@github-actions github-actions bot added the Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants