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

Defaulting TimeData to "now" has offset issues #941

Open
ctsims opened this issue Oct 27, 2020 · 0 comments · Fixed by #942
Open

Defaulting TimeData to "now" has offset issues #941

ctsims opened this issue Oct 27, 2020 · 0 comments · Fixed by #942

Comments

@ctsims
Copy link
Member

ctsims commented Oct 27, 2020

A form created where a TimeData question has the default value of

format-date(now(), '%H:%M:%S')

should be initialized to the current time, but doing so on Oct 27, 2020 in the US Eastern timezone (likely others) results in the value being displayed to the user being 1 hour early (10am v. 11am, etc).

This is quite likely because the time value is being cast against an Epoch date in one instance (which is UTC-5 in US Eastern on Jan 1) and against the current date in another (which is UTC-4 in US Eastern on Oct 27)

@ctsims ctsims changed the title Defaulting TimeData to "now Defaulting TimeData to "now" has offset issues Oct 27, 2020
@ctsims ctsims linked a pull request Oct 28, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant