| 20:56 | <justingrant> | 402 friends: in today's plenary meeting, we were unable to reach consensus on https://github.com/tc39/proposal-temporal/pull/2479. There are currently no comments from TG2 folks in that PR, nor in the original issue https://github.com/tc39/proposal-temporal/issues/2013 that's been open for more than a year. Could I humbly ask that comments be added into the PR ASAP (ideally today, or tomorrow morning) to explain any objections? This is not a complex change so hopefully it should be a quick review. If there are no (or easy-to-resolve) objections, then maybe we could ask again for consensus during the overflow topic we already have planned for later in this plenary week. To summarize the change:
It's OK if there are blocking issues with the proposed fixes above, but we're all working very hard to close down any remaining open issues in Temporal. We really want to get the near-final form of this proposal into polyfill users' hands ASAP so we can ensure that no other regressions or problems come up. I realize this is just one PR among many, but we're down to hopefully the last few issues so every one we resolve this week will be helpful to the general goal of getting Temporal ready to ship. Thanks! |
| 21:09 | <sffc> | It may be useful to add this to the 402 agenda next week if you can't get consensus before then |
| 21:10 | <sffc> | It looks overall okay. Not sure about the semantics of conflicting time zones. I think it's fine. |
| 21:11 | <justingrant> | Ideally we could get a quick review before then (before the TC39 plenary is over). If there are substantial objections that can't be quickly resolved offline, then it's OK to bring to the 402 meeting but if there's no objections just not reviewed yet, I was hoping we could move fwd in this plenary. |
| 21:11 | <sffc> | I thought I recalled us discussing that conflicting time zones would simply be ignored? |
| 21:12 | <justingrant> | I thought I recalled us discussing that conflicting time zones would simply be ignored? |
| 21:16 | <ptomato> | I don't remember anything like that, but I'll look in the notes |
| 21:20 | <sffc> | https://github.com/tc39/ecma402/issues/750 |
| 21:21 | <ptomato> | oh, I see now you were proposing it there - I must have missed that due to the other question about the bug |
| 21:30 | <sffc> | I think the main footgun is if the datetime formatter is configured to not display the time zone. Because then there's not a way for the user to tell what time zone the date is being displayed in. |
| 22:29 | <justingrant> | Shane, is there a specific behavior change that you'd recommend in that case? And would you want to see that behavior in ZonedDateTime.p.toLocaleString() too? |
| 22:36 | <ptomato> | Is it possible to create a formatter with `{timeZoneName: "none", timeZone: "America/McMurdo"}`? |