Re: [w3ctag/design-reviews] Temporal proposal (#311)

Taken up during the Iceland F2F. We have one hard requirement for this to ship, in particular the WebIDL dependency should be solved. Additionally, timezone lookup seems like a missing piece in the infrastructure, and that would be a useful addition. The fingerprinting concerns we believe are not significant, as it would be bound to a browser version which is already detectable in the user agent string.

Additional feedback we have are the following points:

Regarding delta, as generating one from two Civil temporal types is hard to define, so we think the current `.plus()` operation should suffice. If there is wide usage of this, and the community needs syntactic sugar this can be revisited later.

As a developer, it is unclear what "Civil" implies; we do not have better suggestions, but it would be useful to either disambiguate that in the spec (or through MDN) what the intent of that name is, and when that name should be used for other types.

When there is wide implementation and usage, we would like to have HTML integration treated as a bug, and revisited.

As for the Gregorian only limitation, turns out that calendars are hard! @dbaron had a bunch of useful feedback on the complexity of this problem, and we are okay with the current approach.

Aside from the concerns above, we are happy to see this move forward and would like you to re-open if there are any significant design changes that we should look at.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/311#issuecomment-494409075