Canada's New Time Zones Crashed Our App Before They Took Effect
Comments on “Canada's New Time Zones Crashed Our App Before They Took Effect”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
A postmortem from one web team describes an app that failed to load for Windows users in western Canada on Chrome, Edge and Electron. Per the author, new Windows time zones for British Columbia, Alberta and Manitoba had no ICU mapping, so Chromium returned undefined from Intl's resolvedOptions().timeZone, and an early telemetry call to .split threw during startup. The fix was optional handling and moving telemetry off the boot path. Most dates and fix statuses were unverified; only Firefox 159's fix matched its source.
Why it ranked
No. 18 of 111 with a score of 0.65. The panel rated it highest on technical depth (0.80) and new information (0.79), lowest on significance (0.49). The judges disagreed most on new information (spread 0.46), so the story is marked contested. Placed No. 18, No. 28 by score alone: the fourth Programming & dev tools story of the day (−0.020). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- A detailed, practical engineering postmortem on a browser time-zone API returning undefined, causing app crashes. Well-explained and actionable, but niche in audience and not landmark-level significance.
- AI judgeJudge 3gpt-5.6-luna
- A well-supported, technically specific postmortem showing how OS/browser time-zone changes and a telemetry initialization dependency caused production crashes, with concrete reproduction, fixes, and broadly useful engineering lessons.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.65total under rubric v2.3Contestedjudges differ by 0.46 on new information
- Significance0.49
- Reader interest0.74
- Audience breadth0.57
- Practical relevance0.78
- Substantiated0.75
- Technical depth0.80
- New information0.79
- Counts against: Promotional0.04
- Counts against: Overclaim0.16
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.58 | 0.30 | 0.58 | 0.49 | 0.28 | +0.24 | +0.117 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.79 | 0.60 | 0.82 | 0.74 | 0.22 | +0.26 | +0.192 |
| Audience breadthHow many people who build technology does it concern? | 0.75 | 0.40 | 0.55 | 0.57 | 0.35 | +0.13 | +0.074 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.97 | 0.60 | 0.78 | 0.78 | 0.37 | +0.22 | +0.172 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.82 | 0.60 | 0.82 | 0.75 | 0.22 | +0.05 | +0.037 |
| Technical depthHow technically substantive is it? | 0.99 | 0.70 | 0.70 | 0.80 | 0.29 | +0.05 | +0.040 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.91 | 0.50 | 0.96 | 0.79 | 0.46 , above the contested threshold | +0.05 | +0.040 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.04 | 0.05 | 0.03 | 0.04 | 0.02 | −0.19 | −0.008 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.19 | 0.20 | 0.08 | 0.16 | 0.12 | −0.11 | −0.017 |
| Sum of contributions | +0.646 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.646 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-10-31/18/"><img src="https://rubric.hrih.si/badge/2026-10-31/18.svg" alt="Ranked #18 on Rubric, 31 Oct 2026" width="245" height="28"></a>Claim check
Claim check: 1 matches source · 1 no source given · 6 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkDate
Microsoft shipped Windows updates in September and October 2026 with new time zones for three Canadian provinces (British Columbia, Alberta, Manitoba).
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “In September and October 2026, Microsoft shipped Windows updates with new time zones for three Canadian provinces”
The source says No passage could be compared.
Source cited by the article: techcommunity.microsoft.com/blog/dstblog/interim-guidance-for-british-columbia-time-zone-changes-2026/4544988
Couldn’t checkNumber
British Columbia, Alberta and Manitoba are moving to permanent daylight saving time, so their clocks won't fall back on November 1, 2026 and will stay on UTC-7 (most of BC), UTC-6 (Alberta) and UTC-5 (Manitoba).
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “On November 1, 2026 their clocks won’t fall back, and they will stay on UTC-7 (most of British Columbia), UTC-6 (Alberta) and UTC-5 (Manitoba) all year round”
The source says No passage could be compared.
Source cited by the article: www2.gov.bc.ca/gov/content/governments/celebrating-british-columbia/daylight-saving-time
No source givenCausal conclusion
When Windows introduces a time zone absent from the browser's ICU mapping data, Chromium returned undefined for the time zone while Firefox fell back to a fixed-offset zone like Etc/GMT+8.
The article gives no link or citation for it.
The article says “Firefox fell back to a fixed-offset zone like Etc/GMT+8, which is an hour wrong, but still a string”
The source says No source to compare with.
Couldn’t checkDate
A TypeScript issue asking to type resolvedOptions().timeZone as string | undefined was closed in 2023 because the spec says it is always a string.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Someone asked to make it string | undefined back in 2023 (TypeScript issue #55869), and it was closed because the spec says it is always a string”
The source says No passage could be compared.
Source cited by the article: github.com/microsoft/TypeScript/issues/55869
Couldn’t checkDate
The missing time zone mappings were added to CLDR and merged into ICU on October 13, 2026.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “the missing mappings were added to CLDR and merged into ICU on October 13, 2026”
The source says No passage could be compared.
Source cited by the article: github.com/unicode-org/icu/pull/4282
Matches sourceVersion
Firefox fixed the issue in Firefox 159, released on October 27, 2026.
The cited source says the same thing.
The article says “Firefox: fixed in Firefox 159, released on October 27, 2026”
The source says “firefox159 | + | verified”
Source cited by the article: bugzilla.mozilla.org/show_bug.cgi
Couldn’t checkVersion
Chromium fixed the issue on October 23, 2026, verified in Chrome 156.0.8078.76 on October 27.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Chromium: fixed on October 23, 2026, and verified in Chrome 156.0.8078.76 on October 27”
The source says No passage could be compared.
Source cited by the article: issuetracker.google.com/issues/570417342
Couldn’t checkGeneralization
The Electron issue was still open at the time of writing.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Electron: still open at the time of writing”
The source says No passage could be compared.
Source cited by the article: github.com/electron/electron/issues/55137
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 2 pts, not on front page
Recorded for context only, checked 31 Oct 2026, 05:46 UTC. It played no part in the ranking.