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
Exploring what would be required for the JS implementation, I'm not sure if it is easily possibly to implement this flag on top of JavaScript's date implementation as this data isn't currently available, and some consistency questions may come up with regards to its implementation.
I am by no means an expert on this topic though, but this was originally mentioned by @ptomato.
The text was updated successfully, but these errors were encountered:
Yeah, also given the feedback provided in #61 (comment), we may want to consider dropping that flag entirely.
Talked with @sunfishcode a little about this yesterday: basic timezone support was intended to follow what POSIX provides. But that's clearly showing its age. We should want to update it to more recent standards where possible, especially because we care about targeting platforms like the web.
I've filed #69 to more broadly discuss changes to the timezones API. It seems daylight savings might be challenging for different reasons too. Let's merge this into the conversation there?
Exploring what would be required for the JS implementation, I'm not sure if it is easily possibly to implement this flag on top of JavaScript's date implementation as this data isn't currently available, and some consistency questions may come up with regards to its implementation.
I am by no means an expert on this topic though, but this was originally mentioned by @ptomato.
The text was updated successfully, but these errors were encountered: