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
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
No
Description
Timepicker is either not using the provided moment adapter or is ignoring the "useUtc" setting. If I set "useUtc" to "true" on the adapter then it works for any Datepicker in the component, but any Timepicker has "_isUtc" set to false.
Even when binding the Datepicker and Timepicker to the same property, changing the Date will instantiate and bind to a new moment object with "_isUtc" set to "true", but changing the Time will instantiate and bind to a new moment object with "_isUtc" set to "false."
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run ng version)
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
No
Description
Timepicker is either not using the provided moment adapter or is ignoring the "useUtc" setting. If I set "useUtc" to "true" on the adapter then it works for any Datepicker in the component, but any Timepicker has "_isUtc" set to false.
Even when binding the Datepicker and Timepicker to the same property, changing the Date will instantiate and bind to a new moment object with "_isUtc" set to "true", but changing the Time will instantiate and bind to a new moment object with "_isUtc" set to "false."
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: