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
Putting the epoch into the value part of the input I get it converted when I click on the field(not automatically though), but placing it inside initialValue: for rome the input field remains blank. It seems to fetch it fine as soon as I click the field, but doesn't initially populate anything.
I had to solve this by adding the timezone offset from moment to the return form. How is it that it simply cannot "just" convert a unix epoch to that particular time without using javascript's time objects, which get localized. Moment already supports changing timezones to force UTC, so adding an option to rome to force a certain timezone should be relatively easy?
Though it would seem this project isn't maintained anymore? @bevacqua
Putting the epoch into the value part of the input I get it converted when I click on the field(not automatically though), but placing it inside initialValue: for rome the input field remains blank. It seems to fetch it fine as soon as I click the field, but doesn't initially populate anything.
<input id="datetime" class="input" data-rome-id="0">
What am I doing wrong here?
The text was updated successfully, but these errors were encountered: