You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, if i try to input an existent value stored onselectedEvent.start crash my browser tab:
<p-calendar [showIcon]="true" dateFormat="dd.mm.yy" [(ngModel)]="selectedEvent.start" [showTime]="!selectedEvent.allDay || false">
the value of selectedEvent.start:Date is "Tue Apr 02 2024 01:25:00 GMT+0300 (Eastern European Summer Time)"
if i use a an empty variable, everything is great
Environment
no
Reproducer
No response
Angular version
17.0.5
PrimeNG version
17.12.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
9.8.1
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered:
So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you open a new issue so we can include it in our roadmap?
Thanks a lot for your understanding!
Best Regards,
Describe the bug
Hello, if i try to input an existent value stored onselectedEvent.start crash my browser tab:
<p-calendar [showIcon]="true" dateFormat="dd.mm.yy" [(ngModel)]="selectedEvent.start" [showTime]="!selectedEvent.allDay || false">
the value of selectedEvent.start:Date is "Tue Apr 02 2024 01:25:00 GMT+0300 (Eastern European Summer Time)"
if i use a an empty variable, everything is great
Environment
no
Reproducer
No response
Angular version
17.0.5
PrimeNG version
17.12.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
9.8.1
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: