- theme.css: colour-scheme per theme for select/input/textarea and explicit
option/optgroup colours (native popup was rendering light text on white in
dark mode); :checked uses the purple tint
- _shared.css: token fallbacks on .mu-pop-* so the theme/language menus stay
readable if tokens fail to load
- VERSION 2026.10.24.7
The share row sat outside .mu-container, so its right edge was 15px from the
viewport while routes/stops pages sit at 43px. Wrapped it in .mu-container —
measured rightGap 43 on /check, same as /routes/:id and /stops/:code.
- ThemeSwitch: auto now follows the device (prefers-color-scheme) with a live
matchMedia listener instead of a 06:00-18:00 clock rule; labels become
'ตามอุปกรณ์ / Device'; auto icon is a monitor
- layout.tsx pre-paint script resolved with matchMedia (no theme flash)
- i18n: default language is Thai (no navigator guess) in lib/ui/i18n.ts;
new 'i18nready' event so LangSwitch syncs its label after runtime boot
(button previously stuck on ไทย when the page loaded in English)
- VERSION 2026.10.24.5
Copied the five edited content files from
web-at-transit-mock/ui/partials/{about-data,blog-data} into
public/content/{about-data,blog-data}; byte-identical (sha256 verified).
Files: about-data text2/text3/text4, blog-data text5/text7.
The Next port reads /content/about-data/ and /content/blog-data/ at runtime,
so no code change was needed.
Verified in the browser at /about and /blog/5 in Thai and English - the new
copy renders and matches the mock's body text exactly.
The mock carried aria.* and other keys the Next port never received, so
Thai/English coverage was 269 keys here against 354 there. Imported all
missing keys from the mock; both locales now match key for key.
Placeholder numbering and aria labels now come from the same source as the
mock.
- .mu-toolbar background: purple gradient -> var(--c-surface) white
- removed #stops-search-btn (filtering already runs live while typing; the
existing JS guarded on the element existing, so nothing else changes)
- #stops-reset-btn ghost -> primary so it renders in brand purple
Verified on both ports at 1280px light theme: toolbar rgb(255,255,255),
no search button, reset button has the purple gradient, back stays ghost.
.mu-hero-panel used a purple gradient with a light border. Now a plain white
surface with a 1px --c-ink border (which resolves to #1f2a44 in light mode and
to the light ink in dark mode so the outline stays visible).
Matches the mock, which uses #ffffff / #1f2a44.
Measured: light rgb(255,255,255) bg + rgb(31,42,68) border on both ports;
dark keeps a readable outline.
Root cause of 'the version is new but the old bug is back'. When the on-screen
numpad CSS was removed earlier, a regex dropped the rule body of
'.mu-search-mode[hidden] { display: none; }' but left the selector. CSS then
parsed the following declarations as belonging to that selector:
.mu-search-mode[hidden],
.mu-search-field { display: flex; ... }
so every mode panel rendered as flex and none of them could be hidden. The
toolbar measured 341px against the mock's 245px on /stops.
Restored the rule body and added '.mu-stop-grid[hidden] { display:none }'
(grid was overriding hidden too, in both repos).
Measured side by side with :8090/ui/#/stops - code/place/near each show only
their own panel, the stop list hides on the near tab, toolbar height matches
within 2px across all four states.
Root cause of 'the change never appears': pages are statically prerendered,
so Next replied with Cache-Control: s-maxage=31536000. The browser kept the
old HTML for up to a year, which is why editing sw.js and the footer version
changed nothing for an existing visitor.
next.config now adds, for any request whose Accept includes text/html:
Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
Static assets are untouched (hashed files under _next/static keep their
immutable caching).
Bumped version.json and the SW VERSION to 2026.10.24.2.
Verified with curl (Accept: text/html) that /, /stops, /routes, /about and
/credits all return no-store, while images still return public, max-age=0;
and in the browser an ordinary reload returns the three-tab /stops page with
the v2026.10.24.2 footer badge.
The service worker version had never moved past 1.0.0 and nothing on the page
said which build was loaded, so an old cached shell looked identical to a
fresh one.
- public/version.json: app, version, builtAt, pwa
- sw.js VERSION -> 2026.10.24.1 (new cache name, old caches dropped on activate)
- next.config: sw.js and version.json are served no-cache, no-store, plus
Service-Worker-Allowed: / ; ui-manifest.json must-revalidate
- layout: <html data-app-version> read from version.json at build time
- PwaBoot: paints the version into the footer badge, polls /version.json
(1.5s then every 5 min) and reloads once when it differs; guards against
reload loops
- footer shows v2026.10.24.1 in mono next to the copyright
Verified: sw.js, /version.json and <html data-app-version> all report
2026.10.24.1, the footer badge shows it, and /stops renders the three search
tabs with the near-me panel in its own tab.
The result container had been left outside #stops-near-wrap and an earlier
selout removed the wrong copy, so on /stops the map and ranked stops were
rendered at the bottom of the page instead of inside the third tab, unlike
the mock at :8090/ui/#/stops.
Now the DOM matches the mock exactly: three tabs, three panels, the location
button and its result inside the near panel, and only Search/Clear/Back in
the toolbar.
Compared side by side against :8090/ui/#/stops - tab order, panel visibility,
active state, list visibility on the near tab, geolocation result (map plus
8 ranked stops), button re-enable and repeat press all identical.
The third tab made the Thai labels wrap on 375px. The tab bar now stretches
its children so all three share the same height, uses centred two-line labels
with a 56px minimum, and keeps zero horizontal overflow at 360/375/414px.
sw.js VERSION 1.0.0 -> 1.0.1 so browsers drop the cached shell and pick up
the three-tab markup without a manual cache clear.
Searching now has three peer modes on /stops: by stop code, by place name,
and by device location.
- StopsView: third tab (data-mode=near) plus its own panel holding the
location button, hint and result area; the button no longer sits in the
toolbar with Search/Reset/Back
- stops.search.ts: setMode handles the near mode, disables the other panels,
hides the full stop list while the ranked results are shown, and skips
filtering in that mode
- stops.nearme.ts: applies the security gate - the tab is revealed only when
window.isSecureContext && navigator.geolocation exist, otherwise it is
hidden and any active near mode falls back to stop-code search
- i18n: stops.modeNear / nearCta / nearHint (th + en, both copies)
Distance is computed from each stop's own coordinates (busstop_list.json)
against the device position, sorted nearest first.
Verified: secure context shows all three tabs and returns a ranked map;
a forced insecure context hides the tab and refuses the mode.
stops.nearme.ts exported a default mount() but PageRuntime only invokes
the default export of stops.init; this module was imported for its side
effects and never called, so the button did nothing at all.
- self-bind on import with a dataset.nearBound guard against double binding
- retry up to ~2s while ATMap finishes loading
- map.ts: re-enable the button after a successful lookup (it stayed
disabled forever, so a second press was impossible)
Verified with geolocation override at 14.5880,100.4530: first press
renders the map plus 8 nearest stops with distances, button re-enables,
second press works, and no duplicated network requests (2 per press).
Previous order was (menu)(theme)(language). Swapped so the row reads
logo ... (theme)(language)(menu) and the hamburger sits flush against the
right padding edge, which is where the thumb menu is expected.
Measured 360/375/414px: brand starts at 14px, menu ends exactly on the
right padding edge, 8px gaps, no horizontal overflow.
On <640px the topbar used flex-wrap: wrap with no spacer, so the brand,
the hamburger and the theme/language buttons all piled up on the left.
- flex-wrap: nowrap at mobile
- .mu-menu gets margin-inline-start: auto and order 1, .mu-topbar-tools order 2
- .mu-brand flex: 1 1 auto with min-width: 0
Measured 360/375/414px: brand starts at 14px, tools end flush at the right
padding edge, 8px gaps, no horizontal overflow. 768/1280px unchanged.
The topbar carried five small buttons in a row (3 theme + 2 language).
Replaced with two single buttons that open their own popover menu:
- ThemeSwitch: single icon button showing the active mode, menu with
light/dark/auto as menuitemradio
- LangSwitch: new component showing the active code (ไทย / EN), menu
keeps the existing [data-i18n-switch] mechanism from i18n.ts
- .mu-topbar-tools wrapper, 8px gap (WCAG 2.5.8), 40px buttons / 44px on touch
- popovers close on select, outside click and Escape (focus returns to button)
Also fixed two bugs found on /stops:
- .mu-btn.outline had no CSS rule, so the browser painted a light grey
background that ignored the dark theme
- deleted the unused StopSearch component which still carried the old
number pad and its delete key, plus the now-unused stops.padDelete key
Verified at 375px: no horizontal overflow, buttons 40x40 and 59x40,
8px gap; menus open/close correctly in both themes.
Share button was themed only in pages/home.css, so /stops, /routes and
/check rendered an unstyled button. Moved to _shared.css and rebuilt as a
ghost variant of .mu-btn:
- radius 12px -> var(--radius) 8px, min-height 44px (48px on touch)
- focus ring #2b2f42 (near-black) -> var(--c-focus)
- LINE link green -> brand purple (DESIGN.md is single-accent)
- hover/active/transition states added
Global scale cleanup (DESIGN.md allows 4px/8px radii only):
- 16 distinct border-radius values -> var(--radius-sm) / var(--radius) / var(--radius-pill)
- 39 distinct font-sizes -> 13-step scale
- outline-offset 1px/2px/3px -> 2px everywhere
- radius and type scale documented in DESIGN.md as enforced tokens
Verified across 4 pages x 2 themes: identical 44x158 button, radius 8px,
contrast 5.80 light / 7.37 dark, no horizontal overflow.
window.AtShare was assigned the module namespace object from
import('./share'), which is frozen. share.init.ts then threw
'Cannot add property refresh, object is not extensible', aborting the
click handler so the share button did nothing on every page.
- runtime.ts: spread the namespace into a plain object
- share.init.ts: expose the updater as window.AtShareRefresh
- home.init.ts / stop.init.ts: call AtShareRefresh
- remove the temporary probe marker from StopView
Verified: /?s=at_main_terminal, /stops/:code?q=, /routes/:id, /check/:id
all produce short links and restore state on load (TH and EN).
- src/lib/site.ts: single source for site name/url/description (rename via env only)
- src/app/robots.ts: allow all, disallow /api /files, explicit Googlebot/Bingbot/DuckDuckBot/Bravebot/Applebot
- src/app/sitemap.ts: static pages + routes/check/stops from backend, falls back to static when API is down
- src/components/JsonLd.tsx: WebSite + Organization + SearchAction, BreadcrumbList, BusStop, Service
- layout.tsx: metadataBase, canonical, keywords, robots, openGraph, twitter
- generateMetadata for /stops/[code], /routes/[routeId], /check/[routeId]
- canonical + description on /stops /routes /blog /about /credits
- public/og-image.png 1200x630
The five code cells are now the only way to enter a stop code. The numpad
was redundant on touch devices (the cells use inputMode=numeric, so the
system keyboard already switches to digits) and it crowded the 375px
layout.
- StopsView.tsx: drop the .mu-numpad markup.
- stops.search.ts: drop initNumpad(), its call and the pad show/hide toggle.
- stops.css: drop all .mu-numpad rules.
tsc clean, npm run build passes.
Android (Samsung S23, One UI 6) refuses 'Install app' / standalone mode
when the origin is not secure or the app has no service worker. The ported
Next.js app shipped neither: only a manifest existed, and no sw.js at all.
- public/sw.js: navigation network-first with an offline fallback,
cache-first for static assets, /api and /files bypassed, versioned
cache with skipWaiting + clients.claim.
- public/offline.html: offline shell.
- src/components/PwaBoot.tsx: registers the worker, wires
beforeinstallprompt into an in-app install button, and shows a
share-sheet hint on iOS/Samsung Internet where the event never fires.
- ui-manifest.json: add id, display_override, prefer_related_applications,
launch_handler, handle_links, a maskable icon for Android 14 and
screenshots for the install preview.
- layout.tsx: viewport-fit=cover, interactive-widget, maximumScale 5
(never user-scalable=no), appleWebApp metadata, format detection off,
and drop manually duplicated meta tags that Next already emits.
Verified: manifest passes 8/8 installability checks, sw.js and offline.html
serve with correct content types, tsc clean, npm run build passes.
Verified each path against every .ts/.tsx/.css under src plus every JSON
under public. Kept all dynamic lookup directories (routes/qrcode/stations/
stops/partners/icons) because the ported modules resolve those per id and
try several extensions at runtime.
Deleted (nothing references them):
- image/extras/boat.jpeg, boat-market2transta.jpg
- image/landmarks/*.{png,jpg} (stations.json has no landmarks[] entries)
- image/icons/minibus-256x256.ico (Next serves app/icon.png instead)
- image/partners/_original/ (local backup of the tcl999 source photo)
public/image: 39.8 MB -> 30.1 MB. npm run build still prerenders all routes.
The merge of origin/main left 13 conflict markers across 9 files under
frontend/src/app, so 'next build' failed with 21 parse errors and the
Docker frontend image never built.
Resolution:
- Keep the HEAD side (views + PageRuntime shell) for all 8 route pages.
- Rebuild layout.tsx by hand: it mixed both sides outside the conflict
blocks (Viewport/headers/langFromCookie were only imported on the
merged-in side). Kept IconSprite/SiteHeader/SiteFooter/SiteBoot,
the mock CSS order (shared -> map -> shell -> responsive), the
vendored K2D and Leaflet links, and set lang="th" because i18n.ts
sets document.documentElement.lang at runtime.
Verified: tsc --noEmit clean, npm run build compiles and prerenders
all 12 static + 5 dynamic routes.
CARGO_BUILD_JOBS=2 on the 1-vCPU VPS spiked load (~30) and destabilised
the swarm during deploy (health checks timed out, Dokploy restarted and
killed the build). Build with a single job; combined with the 4 GB
swapfile added on the host this keeps the build from starving services.
Deploy failed on the VPS:
error: rustc 1.88.0 is not supported by the following packages:
[email protected].0 requires rustc 1.89.0
No Cargo.lock is committed, so cargo resolves the newest crates on every
build; the transitive MSRV has moved past the 1.88 builder. Bump to
rust:1.90-bookworm (>= uuid 1.28's required 1.89).