diff --git a/docs/ANNOTATION-RENDERING.md b/docs/ANNOTATION-RENDERING.md index 8cd2a2b0..46841f21 100644 --- a/docs/ANNOTATION-RENDERING.md +++ b/docs/ANNOTATION-RENDERING.md @@ -244,29 +244,30 @@ the strip is not sticky. The drawing column (U2 Task 17: the view chips, the tools and the canvas box, the add row, the message line; `data-drawing-column`) is pinned under the strip -from 1 024 px wide and 40.25 rem (644 px) high: `sticky` at -`--edit-pinned-top` (bar + strip + 0.75 rem, the strip's gap), aligned to the -start of its grid row, so no part of it ever passes under the strip or the bar -while the side panel scrolls past; the side panel still passes under the strip. -A bottom margin of −3 rem lets the pinned travel run into the page's bottom -space (the workspace's gap and the main area's padding), else the end of the -page pushed the column's top under the strip at 1 180 × 820. So that the column -always fits the window, the canvas box (`data-canvas-box`) is capped in width at +from 1 024 px wide and 40.25 rem (644 px) high: `sticky` at `--edit-pinned-top` +(bar + strip + 0.75 rem, the strip's gap), aligned to the start of its grid row, +so no part of it ever passes under the strip or the bar while the side panel +scrolls past; the side panel still passes under the strip. A bottom margin of +−3 rem lets the pinned travel run into the page's bottom space (the workspace's +gap and the main area's padding), else the end of the page pushed the column's +top under the strip at 1 180 × 820. So that the column always fits the window, +the canvas box (`data-canvas-box`) is capped in width at `(100svh − --edit-pinned-top − 9.25 rem) × 4/3 + 2 px` (9.25 rem: one row of chips, one add row, the line and the gaps; 2 px: the box's border), keeping its -4:3 ratio: the cap follows the window's small viewport height, never the -scroll nor a collapsing browser toolbar. The box is unchanged when the browser -window (not the screen) is 1 024 × 768, 1 180 × 820 or 1 280 × 800, and smaller -in shorter windows (capped below 672, 789 and 672 px of window height at those +4:3 ratio: the cap follows the window's small viewport height, never the scroll +nor a collapsing browser toolbar. The box is unchanged when the browser window +(not the screen) is 1 024 × 768, 1 180 × 820 or 1 280 × 800, and smaller in +shorter windows (capped below 672, 789 and 672 px of window height at those widths; a tablet's browser toolbars take their height off the screen's); a -capped box sits left, with spare width on its right. The column's focusables carry -only the bar's margin there (the strip's margin, larger than the pinned top, would -scroll the page on a focus of a pinned control). The 9.25 rem -assumes one row of view chips: a sheet whose chips wrap to a second row makes the column -about 38 px taller than the cap allows, so where the cap binds the column's top goes -under the strip at the end of the page. Below 644 px of window height the tool column -(365 px) no longer fits beside a capped box: nothing is pinned or capped, and the -drawing scrolls under the strip as before, with the strip's margin on its focusables. +capped box sits left, with spare width on its right. The column's focusables +carry only the bar's margin there (the strip's margin, larger than the pinned +top, would scroll the page on a focus of a pinned control). The 9.25 rem assumes +one row of view chips: a sheet whose chips wrap to a second row makes the column +about 38 px taller than the cap allows, so where the cap binds the column's top +goes under the strip at the end of the page. Below 644 px of window height the +tool column (365 px) no longer fits beside a capped box: nothing is pinned or +capped, and the drawing scrolls under the strip as before, with the strip's +margin on its focusables. The editor page's other focusables (criterion 25: the header's « Enregistrer », the tab row, « Défaire » and « Refaire », the notices' controls) carry a smaller margin, diff --git a/docs/development/V1-2-6_OWNER_TRIAL.md b/docs/development/V1-2-6_OWNER_TRIAL.md index 9162e926..f7b7ded6 100644 --- a/docs/development/V1-2-6_OWNER_TRIAL.md +++ b/docs/development/V1-2-6_OWNER_TRIAL.md @@ -686,7 +686,7 @@ d'essai (rôle `admin` et habilitation `sheet_editor`), double authentification `docs/design/v1-2-6-u2/` (arbitrages A1 à A15). U2 n'ajoute aucune migration : la pile garde ses données, l'application sert le code de cette branche. Claude n'écrit rien sur la pile d'essai : vous lancez vous-même les commandes. -Décisions du 19 novembre 2026, enregistrées telles que vous les avez prises : +Décisions du 19 novembre 2026, résumées ici (votre texte intégral est dans le contrat de U2, addendum 2) : - D1, validée : la raison d'un « Défaire » ou d'un « Refaire » indisponible s'affiche dans une petite bulle sous le bouton, au toucher, à la souris et au clavier, sans rien déplacer. - D2, validée : la marge de focus de l'éditeur (le focus clavier s'arrête sous la barre du haut) vaut à toutes les @@ -816,11 +816,12 @@ Tablette en paysage (au moins 1 024 px de large ; en dessous, l'éditeur est en un contrôle du dessin qui ferait défiler la page. 19. Refaire retenu. Préparez quelque chose à défaire et à refaire : créez un point, déplacez-le d'un pas aux flèches validé par Entrée, puis « Défaire ». Action : outil « Zone », posez un sommet (la boîte de « Point » s'ouvre tout - de suite et cache l'en-tête : prenez « Zone »), puis donnez le focus à « Refaire » puis à « Défaire » : un lecteur - d'écran lit la raison. Appuyez dessus : la raison s'affiche dans une bulle sous le bouton et rien d'autre ne se passe. Puis - « Annuler le tracé », reprenez l'outil « Sélectionner et déplacer », déplacez le point par deux flèches sans - valider et cliquez « Refaire » à la souris : la raison s'affiche, la série reste en attente. Cliquez - « Défaire » : la série est annulée, et « Refaire » remet le déplacement d'un pas. Sans rien à refaire, « Refaire » reste grisé sans phrase. + de suite et cache l'en-tête : prenez « Zone »), puis donnez le focus à « Refaire » puis à « Défaire » : un + lecteur d'écran lit la raison. Appuyez dessus : la raison s'affiche dans une bulle sous le bouton et rien d'autre + ne se passe. Puis « Annuler le tracé », reprenez l'outil « Sélectionner et déplacer », déplacez le point par deux + flèches sans valider et cliquez « Refaire » à la souris : la raison s'affiche, la série reste en attente. Cliquez + « Défaire » : la série est annulée, et « Refaire » remet le déplacement d'un pas. Sans rien à refaire, + « Refaire » reste grisé sans phrase. 20. La bulle. Action : avec « Refaire » retenu (étape 19), appuyez dessus à la souris, au doigt, puis au clavier (Entrée, Espace). Attendu : une bulle apparaît sous le bouton, entière dans la fenêtre et sous la barre du haut ; rien ne bouge, ni le dessin ni la bande, et la page ne s'élargit pas. Elle se ferme quand la retenue prend fin, @@ -962,8 +963,8 @@ travail ni sur la fiche historique, avec Chromium sur ordinateur et un processeu d'un glisser au doigt avec la loupe a une médiane de 3,0 ms et un p95 de 4,3 ms, loin des 16 ms d'une image ; - le délai d'enregistrement d'un geste (2026-11-19, version de production, souris) : du relâchement de la souris à l'image où la nouvelle forme est affichée et où « Défaire » est disponible, trois essais par geste. Médiane et - maximum sur le code final : glisser d'un sommet 182,5 et 199,9 ms, « + » 176,3 et 183,1 ms, « − » 173,8 et - 177,1 ms, sous la limite de 500 ms. + maximum sur le code final : glisser d'un sommet 173,2 et 199,2 ms, « + » 184,1 et 185,5 ms, « − » 168,7 et + 185,6 ms, sous la limite de 500 ms. Ces chiffres viennent d'un navigateur piloté par ordinateur. Le vrai contrôle est votre essai sur la tablette : si un glisser, un « + » ou un « − » vous paraît lent ou saccadé, notez le geste et la vue. diff --git a/docs/development/V1-2-6_UX_PLAN.md b/docs/development/V1-2-6_UX_PLAN.md index 6be69d79..af81e8bc 100644 --- a/docs/development/V1-2-6_UX_PLAN.md +++ b/docs/development/V1-2-6_UX_PLAN.md @@ -478,8 +478,8 @@ Status: implemented on `feature/v1-2-anatomical-sheets` (lots A to H; Lot I, gat ### U2 · Direct manipulation of points and polygons -- Status: implemented on `feature/v1-2-anatomical-sheets` (plan `.claude/tasks/plans/2026-11-17-v1-2-6-u2.md`, rev 4, - Tasks 1 to 16 and the final fix rounds done; gates ran on the final code, da8642dd, figures in +- Status: implemented on `feature/v1-2-anatomical-sheets` (plan `.claude/tasks/plans/2026-11-17-v1-2-6-u2.md`, rev 4 + then rev 5, Tasks 1 to 20 and the final fix rounds done; gates ran on the final code, 3d6aacad, figures in `V1-2-6_UX_TESTS.md`; owner trial pending). The boards are `docs/design/v1-2-6-u2/` (A1 to A15 and the three adjustments, validated 2026-11-17). - Objective: boards 02 to 06, 13 and 31 to 33 of `v1-2-6-u2/` for points and polygons (curve handles excluded, curves diff --git a/docs/development/V1-2-6_UX_TESTS.md b/docs/development/V1-2-6_UX_TESTS.md index 0a877050..acff3ce7 100644 --- a/docs/development/V1-2-6_UX_TESTS.md +++ b/docs/development/V1-2-6_UX_TESTS.md @@ -50,7 +50,7 @@ Implemented (contract `.claude/tasks/contracts/2026-11-06-v1-2-6-ux-u1-1123.md`) ## U2 · Points and polygons -Implemented (plan `.claude/tasks/plans/2026-11-17-v1-2-6-u2.md`, rev 4 then rev 5 (owner decisions D1 to D5, 2026-11-19); boards `docs/design/v1-2-6-u2/`, A1 to A15 and the three adjustments). Rule numbers (R-n) are the plan's. Gates (plan Task 16) on the final head, 2026-11-19 (code at da8642dd, this page's figures added after): `pnpm check:all` exit 0 (app 2 140, core-wasm 67, supabase 182 tests, e2e:ui 253); the shell suite without `editor-equine.spec.ts` 330 passed, 17 failed, 5 not run, all in four files outside the editor (figures of the rev 4 code; figures on the final code to be added by the controller). These environment failures are named with their evidence and are not resolved; none is presented as formally independent of U2. Owner decision D5 (2026-11-19): they do not block the manual trial. `admin` (6): timeouts that the 56c75b1 baseline log also shows (sandbox data); no further attribution. `catalogue-integrity` (6): not attributed to U2. The pre-U2 commit 56c75b1 fails the same 6 of 6 tests, on the same assertion, with the same timings, on the same data (2026-11-19, one worker, read-only counts, nothing deleted); the published versions rose from 426 to about 690 in a day of runs, and the failing set grew from 4 to 6 in both trees, so volume is the inferred cause (the card list loads every card before the search narrows it past the 10 s wait). Volume causation is inferred from that trend and the identical baseline, not isolated: a low-volume run needs a reset, which D4 forbids. `catalogue` (3) and `admin-sheets-list` (2): « Target crashed » under the parallel run; both pass 16/16 with one worker (`--workers=1`, 2026-11-19); the logs show nothing more. `pnpm db:sandbox test` 105 passed, 10 skipped, and `test-db` Files=21 Tests=1958 FAIL on `014_animals_relations` (2) and `021_sheet_verification_jobs` (23), identical to before U2, which changes no SQL (run at 0aa0f6bc). The sandbox is never reset or rebuilt on this work (D4). Both opt-in measures rerun (figures in the Performance row). The owner trial is pending. The suites run on the sandbox only (`pnpm db:sandbox`). +Implemented (plan `.claude/tasks/plans/2026-11-17-v1-2-6-u2.md`, rev 4 then rev 5 (owner decisions D1 to D5, 2026-11-19); boards `docs/design/v1-2-6-u2/`, A1 to A15 and the three adjustments). Rule numbers (R-n) are the plan's. Gates (plan Task 16) on the final code, 3d6aacad, 2026-11-19: `pnpm check:all` exit 0 (app 2 158, core-wasm 67, supabase 182 tests, e2e:ui 253); the shell suite without `editor-equine.spec.ts`, on two workers (`--workers=2`; a run at the default count was stopped for lack of memory on the machine), 347 passed, 13 failed, 234 skipped, all in three files outside the editor (on the rev 4 code, da8642dd: 330 passed, 17 failed, 5 not run, in four files). These environment failures are named with their evidence and are not resolved; none is presented as formally independent of U2. Owner decision D5 (2026-11-19): they do not block the manual trial. `admin` (6): timeouts that the 56c75b1 baseline log also shows (sandbox data); no further attribution. `catalogue-integrity` (6): not attributed to U2. The pre-U2 commit 56c75b1 fails the same 6 of 6 tests, on the same assertion, with the same timings, on the same data (2026-11-19, one worker, read-only counts, nothing deleted); the published versions rose from 426 to about 690 in a day of runs, and the failing set grew from 4 to 6 in both trees, so volume is the inferred cause (the card list loads every card before the search narrows it past the 10 s wait). Volume causation is inferred from that trend and the identical baseline, not isolated: a low-volume run needs a reset, which D4 forbids. `catalogue` (3) and `admin-sheets-list` (2): « Target crashed » under the parallel run; both pass 16/16 with one worker (`--workers=1`, 2026-11-19); the logs show nothing more; neither crashed in the two-worker run on 3d6aacad. `animals` (1, new on 3d6aacad): axe reports a colour contrast on the two buttons of the archive confirmation, at 375 px; intermittent, 1 failure in 12 runs of that journey (`--repeat-each=3`, one worker). A centred dialog renders as before U2 (the `Dialog.tsx` change only places an anchored one); the inferred cause is axe measuring during the entrance fade, which the helper's wait on Web Animations does not see. Inferred from the code, not reproduced on 56c75b1, so not attributed. `pnpm db:sandbox test` 105 passed, 10 skipped, and `test-db` Files=21 Tests=1958 FAIL on `014_animals_relations` (2) and `021_sheet_verification_jobs` (23), identical to before U2, which changes no SQL (run at 0aa0f6bc). The sandbox is never reset or rebuilt on this work (D4). Both opt-in measures rerun (figures in the Performance row). The owner trial is pending. The suites run on the sandbox only (`pnpm db:sandbox`). | Kind | Tests | |---|---| @@ -65,7 +65,7 @@ Implemented (plan `.claude/tasks/plans/2026-11-17-v1-2-6-u2.md`, rev 4 then rev | Keyboard | create a zone, add and remove a vertex, move the zone, validate, without a pointer; « + » inserts and Backspace removes on a focused vertex, Backspace after an undo acts on the same focused handle; Ctrl+Z on a focused handle after arrow moves only cancels the preview and a later Enter commits nothing stale; after undoing « + », « − » never removes the wrong vertex; « Désélectionner » commits a pending series | | Paths (T16) | a path annotation gets no handle, no « + » or « − », no zone move in either mode, no keyboard move; its `d` is byte-identical after every gesture on its neighbours, a save and a reload; « Remplacer par un polygone » stays the only change: explicit, validated by the core, the path kept while tracing, on Escape and on a refusal; one undo entry restoring the exact `d`, redo restoring the polygon (owner, BDR-101) | | Accessibility | axe on selection, tracing, move states and the dialog in read and edit modes; handle names (« Point {nom} », « Sommet {n} de {nom} », « Ajouter un sommet après le sommet {n} de {nom} », « Retirer le sommet {n} de {nom} », the handle group « Sommets de {nom} »); live-region message after a move; WCAG 2.5.7: the move mode with four arrow buttons is the single-pointer path without dragging (A11) | -| Performance | commit latency under the 500 ms budget for drag, insert and remove, a measure run by hand at the gates (`e2e/support/measure-commit.ts`, `editor-measure-commit.spec.ts`, `MEASURE_COMMIT=1`) on a run-seeded equine-sized draft, never on the historical copy nor through `editor-equine.spec.ts`. Measured 2026-11-18 on a production build under `vite preview`, Chromium mouse at 1 280 px, CPU ×4, from the release to the painted frame showing the new geometry with the undo entry; on the final code (da8642dd, 2026-11-19): median / max drag 182.5 / 199.9 ms, « + » 176.3 / 183.1 ms, « − » 173.8 / 177.1 ms (three runs each; 15b23f8 and earlier figures in plan Task 10); the drag smoothness is a measure, not an assertion (`e2e/support/measure-drag.ts`, `editor-measure-drag.spec.ts`, run by hand). Measured 2026-11-18 on a production build under `vite preview`, Chromium touch at 1 180 px, CPU ×4: frame work p95 3.9 to 4.5 ms with the loupe (technique A, final code 15b23f8; 4.2 to 4.7 ms before), 4.0 to 4.4 ms outline only (B), 3.6 to 4.2 ms without a loupe; technique A kept. Rerun on da8642dd (2026-11-19, same setup): touch with the loupe, handler to frame median 3.0 ms, p95 4.3 ms (event to frame median 27.8 ms, p95 30.3 ms); mouse, handler to frame p95 3.1 ms. The figures are in plan Task 8; the owner's tablet trial is the real check | +| Performance | commit latency under the 500 ms budget for drag, insert and remove, a measure run by hand at the gates (`e2e/support/measure-commit.ts`, `editor-measure-commit.spec.ts`, `MEASURE_COMMIT=1`) on a run-seeded equine-sized draft, never on the historical copy nor through `editor-equine.spec.ts`. Measured 2026-11-18 on a production build under `vite preview`, Chromium mouse at 1 280 px, CPU ×4, from the release to the painted frame showing the new geometry with the undo entry; on the final code (3d6aacad, 2026-11-19): median / max drag 173.2 / 199.2 ms, « + » 184.1 / 185.5 ms, « − » 168.7 / 185.6 ms (three runs each; da8642dd: 182.5 / 199.9, 176.3 / 183.1, 173.8 / 177.1 ms; 15b23f8 and earlier figures in plan Task 10); the drag smoothness is a measure, not an assertion (`e2e/support/measure-drag.ts`, `editor-measure-drag.spec.ts`, run by hand). Measured 2026-11-18 on a production build under `vite preview`, Chromium touch at 1 180 px, CPU ×4: frame work p95 3.9 to 4.5 ms with the loupe (technique A, final code 15b23f8; 4.2 to 4.7 ms before), 4.0 to 4.4 ms outline only (B), 3.6 to 4.2 ms without a loupe; technique A kept. Rerun on 3d6aacad (2026-11-19, same setup): touch with the loupe (55 of 57 samples), handler to frame median 3.0 ms, p95 4.3 ms (event to frame median 26.0 ms, p95 36.2 ms); mouse, handler to frame p95 4.0 ms (da8642dd: 3.0 / 4.3 ms, event 27.8 / 30.3 ms, mouse 3.1 ms). The figures are in plan Task 8; the owner's tablet trial is the real check | ## U3 · Category panel and own colour