issues
search
tc39
/
proposal-canonical-tz
TC39 Proposal (stacked on Temporal) to improve handling of changes to the IANA Time Zone Database
Other
38
stars
2
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Add ToTemporalTimeZoneSlotValue in TimeZone.p.equals
#42
ptomato
closed
11 months ago
0
Temporal.TimeZone.prototype.equals: Missing call to ToTemporalTimeZoneSlotValue
#41
ptomato
closed
11 months ago
8
Temporal.TimeZone.prototype.equals: Missing call to ToTemporalTimeZoneSlotValue
#43
anba
closed
11 months ago
3
Refactor TimeZoneEquals from @ljharb feedback
#40
justingrant
closed
1 year ago
0
FrankYFTang's feedback about the current spec text
#39
FrankYFTang
closed
1 year ago
13
Catch up with upstream proposal-temporal
#38
justingrant
closed
1 year ago
0
ECMA-262 editors' Stage 3 review
#37
justingrant
closed
1 year ago
9
Editorial: refactor early returns in TimeZoneEquals
#36
justingrant
closed
1 year ago
0
@ljharb Stage 3 review
#35
justingrant
closed
1 year ago
6
@dminor Stage 3 review
#34
justingrant
closed
1 year ago
7
@ptomato Stage 3 review
#33
justingrant
closed
1 year ago
5
Update Temporal submodule
#32
justingrant
closed
1 year ago
0
Rebase spec text to 262
#31
justingrant
closed
1 year ago
0
Normalize SystemTimeZoneIdentifier offset strings
#30
justingrant
closed
1 year ago
0
Add tests for ZonedDateTime and Intl.DTF
#29
justingrant
closed
1 year ago
0
Update polyfill and tests
#28
justingrant
closed
1 year ago
0
Delegate test running to temporal submodule
#27
justingrant
closed
1 year ago
0
Rebase spec text to Temporal
#26
justingrant
closed
1 year ago
0
Use `Etc/Unknown` (like ICU does) to handle the case when the OS's time zone is unrecognized by ECMAScript
#25
justingrant
closed
1 year ago
17
Update Test262 tests
#24
justingrant
closed
1 year ago
0
Add initial polyfill and tests
#23
justingrant
closed
1 year ago
0
Does any ECMAScript engines currently return offset-string time zones from DefaultTimeZone?
#22
justingrant
closed
1 year ago
2
Should identifiers that resolve to UTC always be canonicalized?
#21
justingrant
opened
1 year ago
3
Prepare for polyfill
#20
justingrant
closed
1 year ago
0
Update name of upstream AO
#19
justingrant
closed
1 year ago
0
Add a submodule for Temporal
#18
justingrant
closed
1 year ago
0
Implementer feedback about waiting period for renamed identifiers like Europe/Kiev=>Europe/Kyiv
#17
justingrant
opened
1 year ago
4
Canonical IANA time zone name for Windows time zones
#16
anba
opened
1 year ago
7
Update InitializeDTF and ZDT.p.toLocaleString
#15
justingrant
closed
1 year ago
0
Add initial spec text
#14
justingrant
closed
1 year ago
0
Cleanup repo
#13
justingrant
closed
1 year ago
1
Notes from 2023-05-04 TG2
#12
sffc
closed
1 year ago
1
Add bug reports from WebKit and Firefox
#11
anba
closed
1 year ago
0
Can we say that what's most important is when the TZID originates in ECMAScript?
#10
sffc
closed
1 year ago
15
How to handle merging of intra-country Zones in TZDB?
#9
justingrant
closed
1 year ago
1
How to define "canonical time zone identifier" in the spec?
#8
justingrant
opened
1 year ago
16
Should `Temporal.TimeZone` objects expose their TZDB version?
#7
justingrant
closed
1 year ago
1
How to reduce cross-implementation incompatibility when new IDs are introduced?
#6
justingrant
opened
1 year ago
20
IANA canonicality and time zones equality
#5
Yqwed
opened
1 year ago
3
Backwards-compatibility for Temporal (not `DTF#resolvedOptions().timeZone`) API changes in this proposal
#4
justingrant
closed
1 year ago
1
Meta: This should be a PR, not a repo
#3
littledan
closed
1 year ago
6
Should `DTF.p.resolvedOptions().timeZone` canonicalize or not?
#2
justingrant
opened
1 year ago
2
Proof of concept: API changes for this proposal
#1
justingrant
closed
1 year ago
1