15 lines
1.1 KiB
Markdown
15 lines
1.1 KiB
Markdown
# TODO — file Chromium login stall upstream
|
|
|
|
**Status:** open (2026-08-17). Symptom on https://bonfire.hacktivism.ch/ is **unsolved** in the operator Chromium profile.
|
|
|
|
Firefox and `curl` work. Chromium stays on the guest homepage (Log in click and `/login` in the address bar).
|
|
|
|
**Upstream:** not a known Bonfire issue. GitHub `org:bonfire-networks` has 0 issues for `pwabuilder-sw` / “service worker login”. PWA tickets (#1292 web push, #1758 widgets) are something else.
|
|
|
|
## Still to do
|
|
|
|
1. File a **bonfire-app** bug (Social **1.0.5**): Chromium + PWA SW (`register("/pwabuilder-sw.js", {scope: "/"})`) can keep `/` and `/login` on the cached guest homepage; guest page also uses `data-live-socket="false"` + `data-phx-link="redirect"` on Log in.
|
|
2. Link this instance as one repro (no secrets). Point at `README.md` § *Login in Chromium* and `2026/2026-08-17--bonfire-chromium-login.md`.
|
|
3. After a GitHub issue exists, put the URL here and in `README.md`; close this TODO.
|
|
|
|
Do **not** treat unregister-SW / Incognito / Firefox as a product fix — those are local workarounds only.
|