PrimeTek
12:00 am for time picker issue #1713
-
|
when I choose 12:00 AM. a value of 12:00:00 is returned instead of 00:00:00. it also applies until 12:59 AM. is this a bug for time picker |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
|
I feel like this has been fixed are you using PR 10.6.3? If not please create a StackBlitz reproducer showing the issue. |
Beta Was this translation helpful? Give feedback.
-
|
I'll do it later but. To replicate the issue manually type 12:00 am (don't
use the arrows since they're fine)on the calendar time picker then observe
as it changes to 12:00pm
…On Sat, Apr 20, 2024, 7:32 PM Melloware ***@***.***> wrote:
I feel like this has been fixed are you using PR 10.6.3? If not please
create a StackBlitz reproducer showing the issue.
—
Reply to this email directly, view it on GitHub
<#1713 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR37BAF5KHGHVRPFT4PSX43Y6JG4RAVCNFSM6AAAAABGOMOIUCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCNZTHAZDK>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Ahh if its typing only you can see there are a bunch of open calendar issues around typing dates in: https://github.com/primefaces/primereact/issues?q=is%3Aissue+is%3Aopen+calendar |
Beta Was this translation helpful? Give feedback.
-
|
But the issue tho is it returns a date object with 12:00:00 instead of
00:00:00 it happens from 12:00 am to 12:59 am only
…On Sat, Apr 20, 2024, 7:39 PM Melloware ***@***.***> wrote:
Ahh if its typing only you can see there are a bunch of open calendar
issues around typing dates in:
https://github.com/primefaces/primereact/issues?q=is%3Aissue+is%3Aopen+calendar
—
Reply to this email directly, view it on GitHub
<#1713 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR37BAEKASZPSS5XDPJ6KLTY6JHWRAVCNFSM6AAAAABGOMOIUCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCNZTHA2TO>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
OK create a StackBlitz and I can take a look. |
Beta Was this translation helpful? Give feedback.
-
|
Oh you're right I tested it on the official prime react website it seems
fine. I think I need to update my module or something
…On Sat, Apr 20, 2024, 8:02 PM Melloware ***@***.***> wrote:
OK create a StackBlitz and I can take a look.
—
Reply to this email directly, view it on GitHub
<#1713 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR37BAFWHSVJW4GK6NG4HITY6JKNDAVCNFSM6AAAAABGOMOIUCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCNZTHE3DC>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot.
…On Sun, Apr 21, 2024, 7:19 PM Melloware ***@***.***> wrote:
Closed #1713 <#1713> as
resolved.
—
Reply to this email directly, view it on GitHub
<#1713>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR37BAG5ILPXFXM3KBCUNRDY6OOCLAVCNFSM6AAAAABGOMOIUCVHI2DSMVQWIX3LMV45UABFIRUXGY3VONZWS33OIV3GK3TUHI5E433UNFTGSY3BORUW63R3GEZDGNBZGA3Q>
.
You are receiving this because you authored the thread.Message ID:
<primefaces/community/repo-discussions/1713/discussion_event/1234907@
github.com>
|
Beta Was this translation helpful? Give feedback.
I feel like this has been fixed are you using PR 10.6.3? If not please create a StackBlitz reproducer showing the issue.