Private
Public Access
Everything is stored and server-rendered in UTC (config.settings.base's TIME_ZONE), so article times, the article detail header, and the dashboard's "last fetched" column were always showing UTC regardless of where the viewer actually is. Article/feed timestamps now render as <time datetime="..."> elements carrying the UTC instant plus a UTC-formatted fallback as their initial text; static/js/localize-times.js reformats them using the browser's own timezone via toLocaleString(), both on page load and after every htmx swap (pagination, the inline article expand, the dashboard's retry action all inject new <time> elements without a full page load). No server-side change needed — this doesn't touch the (currently unused) per-user timezone field, and works correctly even if the viewer travels or changes their system timezone, with no settings page required. Verified live in the browser against a UTC-stored timestamp rendering correctly shifted to the sandbox's local zone. Known related issue, out of scope here: the stream's "Received today/yesterday" date-group headers (apps.reader.views._group_by_date) are still computed server-side via timezone.localdate(), which is also effectively UTC — an article just before/after UTC midnight could land in a date group that doesn't match its now-correctly-localized time-of-day. Flagged for the user rather than fixed, since correcting it properly would mean moving date-grouping to the client too. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
42 lines
1.6 KiB
JavaScript
42 lines
1.6 KiB
JavaScript
(function () {
|
|
// Everything is stored and server-rendered in UTC (config.settings.base
|
|
// TIME_ZONE) — these <time datetime="..."> elements carry that UTC
|
|
// instant plus a UTC-formatted fallback as their initial text, and this
|
|
// reformats them using the browser's own timezone, client-side, so the
|
|
// server never needs to know (or guess) where the viewer actually is.
|
|
var SHORT_OPTIONS = { hour: "numeric", minute: "2-digit" };
|
|
var LONG_OPTIONS = {
|
|
year: "numeric",
|
|
month: "short",
|
|
day: "numeric",
|
|
hour: "2-digit",
|
|
minute: "2-digit",
|
|
};
|
|
|
|
function localizeTimesWithin(root) {
|
|
if (!root || typeof root.querySelectorAll !== "function") return;
|
|
root.querySelectorAll("time[data-local-format]").forEach(function (el) {
|
|
var iso = el.getAttribute("datetime");
|
|
if (!iso) return;
|
|
var date = new Date(iso);
|
|
if (isNaN(date.getTime())) return;
|
|
var options = el.dataset.localFormat === "short" ? SHORT_OPTIONS : LONG_OPTIONS;
|
|
try {
|
|
el.textContent = date.toLocaleString(undefined, options);
|
|
} catch (e) {
|
|
/* Intl unavailable or threw — leave the server-rendered UTC text as-is */
|
|
}
|
|
});
|
|
}
|
|
|
|
localizeTimesWithin(document);
|
|
|
|
// Article rows/content are frequently swapped in by htmx (pagination,
|
|
// the inline expand-article view, the dashboard's retry action) without
|
|
// a full page load, so every swap needs the same pass over just the
|
|
// new content.
|
|
document.body.addEventListener("htmx:afterSwap", function (event) {
|
|
localizeTimesWithin(event.target);
|
|
});
|
|
})();
|