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: ion datetime forces to local time without options for backwards compatibility #19401
Comments
We could have an optional prop for |
Thanks for the feature request. @daem0ndev's approach sounds good. I imagine it would look something like this:
If Example of forcing all values to be displayed in UTC:
edit: spoke with @daem0ndev offline, and we decided |
PR coming in soon! thanks ionic team!!! |
after discussing with @liamdebeasi we are going to go with a prop name of displayTimezone instead of just timezone to make it clear that this is only the timezone to be respected for display. The input and output values will always be in UTC (current behavior) |
PR is up! |
Thanks for the issue. This has been resolved via #19519 and will be available in an upcoming release of Ionic Framework. |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Bug Report
[x] 4.9.1
Current behavior:
With the more recent releases of ionic, ion datetime now always converts the date to the system's timezone. This is not backwards compatible with previous behaviour and there is no option for configurability.
Expected behavior:
Ion datetime needs to be enhanced so that backwards compatibility is supported.
Steps to reproduce:
N/A Just want backwards compatibility (ie there should be an option to allow datetime to behave as it did before all the changes with respecting timezones).
Related code:
Other information:
Ionic info:
The text was updated successfully, but these errors were encountered: