docs(docs): R2 limits after rev 4, sign-out notice, desktop leave check

This commit is contained in:
bchanot committed 2026-11-14 19:04:56 +01:00
1 parent ec314af009
commit 55608b2200
2 files changed
+40 -23

No files matched your search

+17 -11
View File
@@ -371,27 +371,33 @@ Adjustments:
- Leave confirmation (`07bebbc`, `579d8af`, `791fc03`): where the browser exposes the Navigation API and the event is
cancelable, a jump of several entries out of the editor with a dirty finding or reference dialog is cancelled and
the top dirty dialog asks « Abandonner les modifications ? ». « Abandonner » runs the jump again with
`traverseTo`, leaving no flag and no notice. With two dirty dialogs the question cascades from the top; the
reference's « Abandonner » also closes the citations sheet so the finding's question is not hidden under it.
Without the API or when the event is not cancelable, the earlier flag and notice stay.
`traverseTo`, leaving no flag and no notice. With two dirty dialogs the question cascades from the top. Before
the finding asks, the citations sheet and a clean reference dialog over it close, so its question is never hidden
under them. Without the API or when the event is not cancelable, the earlier flag and notice stay.
- Notice after the loss elsewhere: unchanged text, now keyed by the session tag.
- Final review, rev 4 (2026-11-14): a Back asks only the layers it removes. A Back that closes only the citations
sheet, or a clean reference dialog over it, closes it and asks nothing, even over a dirty finding form. A Back or a
jump that removes the dirty finding dialog first closes the clean layers over it, so its question is visible and
focused. A sign-out, or a session ending, while a dialog holds unsaved text leaves one flag with no text, keyed by
the sheet id and by a fingerprint of the account salted with a random value stored in the flag: the same account's
next sign-in in this tab shows the notice once on that sheet, another account never matches. The session record's
fingerprint is salted with its own tag; a record of the older, unsalted shape reads as none and rotates.
Support of the confirmation (what `task-8-report.md` of the run proves): verified on Chromium desktop (the pinned
Playwright Chromium, a history jump through the DevTools protocol, one dirty dialog and two stacked); the fallback
logic is covered by unit tests (no API, non-cancelable event). Not verified: Firefox, Safari, Android Chrome on a
real phone, a click in the real toolbar history menu. The http-origin restore is proved by a unit test only.
logic is covered by unit tests (no API, non-cancelable event). Not verified: Firefox, Safari, a click in the real
toolbar history menu (editing needs 1 024 px, so a phone never reaches this case). The http-origin restore is proved by a unit test only.
Accepted limits (owner, 2026-11-14):
1. A move made in the same instant as a pending Back can be swallowed (not reachable at human speed).
2. « Aller à » a finding opens its dialog in view mode.
3. The search of the References tab is kept across tabs (not in the history; « Tout afficher » clears it).
4. The first tap outside the open « Plus » menu only closes it.
5. A sign-out made while a dialog holds unsaved text (from another tab, for instance) leaves no notice later: the tag
rotates and its flags are cleared for account separation.
6. In the leave cascade, « Continuer la saisie » on a lower dialog keeps that draft; a draft already abandoned above
stays dropped (the user's choice), and one Back then reopens the citations sheet.
7. Android Back closing « Plus » relies on `CloseWatcher` and is proved by a stub test only (limit 6 above).
8. BLK-015 and `admin.spec.ts`: tracked apart (RR-13), unchanged.
5. In the leave cascade, « Continuer la saisie » on a lower dialog keeps that draft; a draft already abandoned above
stays dropped (the user's choice). The sheet and a clean reference dialog over the finding close before its
question; one Back then reopens the citations sheet.
6. Android Back closing « Plus » relies on `CloseWatcher` and is proved by a stub test only.
7. BLK-015 and `admin.spec.ts`: tracked apart (RR-13), unchanged.
Lifted by this round: the dead Back after a deletion (finish limit 1) and the focus lost to the page body after a
« Plus » choice (finish limit 8). Changed: the account id left the history entries for the session tag; a multi-entry