T14.3 (D26, BL-061): the sync badge shows the true state and gets out of the way
The badge words live in one function, badgeModel(). States: sending, retrying, held for sign-in, not saved on this device, rejected (with the reason), read and queue, another person's changes, and all sent. Every state names the project. Sign in is a real link to login.html?next=. Dismiss is a real button and removes only the changes the project refused. Both are 44px or more with a focus ring. BL-061: the console pages (Admin, User Directory) never show the badge. All sent shows only after real work. The badge picks a free spot on the screen. One very dense screen case is left and logged as BL-072. tests/sync_badge_check.py (87 checks). autosave_check reads the new badge words.
This commit is contained in:
@@ -696,6 +696,8 @@ deliberately deferred.
|
||||
- **Suggested wave or follow-up:** wave 14, alongside T14.1's badge changes:
|
||||
do not show the badge on pages with nothing to sync, and keep it clear of
|
||||
page controls.
|
||||
- **Status:** fixed at T14.3 (2026-10-17). The console pages never show the badge, "Everything sent" shows only
|
||||
after real work, and the badge moves to a free spot. One dense-screen case is left: BL-072.
|
||||
|
||||
### BL-069 - The sync has no cap on one run and no last-admin guard
|
||||
|
||||
@@ -838,3 +840,16 @@ boundary"). Do not use `localStorage` as the store of record.
|
||||
- **Why not now:** it is a test-script quirk and not part of D18. The documented usage lines show `http://localhost:8000`.
|
||||
- **Suggested wave or follow-up:** next housekeeping pass: use the domain `localhost.local` for a dotless host,
|
||||
or change the usage lines to `127.0.0.1`.
|
||||
|
||||
### BL-072 - The sync badge can cover a control on a very dense screen
|
||||
|
||||
- **Found during:** T14.3 (D26, BL-061)
|
||||
- **Where:** `html/project-data.js` `placeBadge()`; seen on `wp-creation-index.html` at 390px
|
||||
- **What:** the badge looks for a free spot on the screen, and it covers no control when the screen has room for it.
|
||||
With the longest state (a change refused by the project, with a long reason) on the creator page at 390px, no free
|
||||
spot of that size exists. The badge then covers the one control it overlaps least ("Load sample data" at the
|
||||
time of the check). The person can press Dismiss, or scroll (the badge moves again within 2 seconds).
|
||||
- **Why not now:** a fixed overlay cannot fix a screen with no gap. The real fix is a layout change: a bar that
|
||||
takes its own space in the page, or a place for it in the shared header. That is a design decision for all pages,
|
||||
not part of T14.3.
|
||||
- **Suggested wave or follow-up:** decide with Nick whether the shared page layout reserves a status line.
|
||||
|
||||
Reference in New Issue
Block a user