bonfire: TODO to file Chromium login stall upstream

This commit is contained in:
Hernâni Marques 2026-08-17 14:59:27 +02:00
parent 3d81e9f0d9
commit 4609035d46
No known key found for this signature in database
GPG key ID: CB5738652768F7E9
3 changed files with 25 additions and 1 deletions

View file

@ -47,4 +47,7 @@ Workaround (this Chromium profile):
Server-side notes (host `~/koopa-bonfire/data/branding/`, not a substitute for unregister): kill-switch `pwabuilder-sw.js`, overlay CSS, login-click JS. Container copies are overwritten on image recreate.
Daylog: `2026/2026-08-17--bonfire-chromium-login.md`.
UI badge **Federation disabled** can still show while `.env` has `FEDERATE=true` (see `2026/2026-07-10--bonfire-federate.md`).
**Unsolved** in operator Chromium. File-upstream TODO: `TODO-chromium-login-upstream.md`.
UI badge **Federation disabled** can still show while `.env` has `FEDERATE=true` (see `2026/2026-07-10--bonfire-federate.md`).
**Upstream (checked 2026-08-17):** not filed as a known Bonfire bug. GitHub `org:bonfire-networks` issues: 0 hits for `pwabuilder-sw` / `service worker login`. PWA tickets are [web push #1292](https://github.com/bonfire-networks/bonfire-app/issues/1292) and [dashboard widgets #1758](https://github.com/bonfire-networks/bonfire-app/issues/1758) — not this Chromium navigation stall. Login-labelled issues are other topics (2FA, Welcome Back button, OAuth).