fix(anatomy): V1-2.2 marker layer and halo outside the drawing's group
Owner-approved lot B (brief 2026-11-01). The composition root is the engine's (namespaces and frame); the drawing's root becomes a group and the marker layer and halo are its siblings, so no root property reaches a marker. Point hitboxes declare stroke none and visibleFill. Census over the reader's whole allowlist; R3 references compared under the declared transform; click proofs in three engines.
This commit is contained in:
1 parent
f1bb19b30b
commit
4f52f5e1c4
23 files changed
+933
-112
No files matched your search
@@ -4,6 +4,11 @@
|
||||
//! uses. Written under `draft/review/app-<view>.svg` so the markers and the framing can be
|
||||
//! compared outside the browser.
|
||||
//!
|
||||
//! Declared difference (V1-2.2, owner brief 2026-10-30): the application draws the drawing in a
|
||||
//! group of its own under an engine root and declares each point hitbox's stroke and capture
|
||||
//! (`compose`, `layer::render_composed_layer`); this review drawing keeps the R5 form, a seed
|
||||
//! resource never regenerated without the owner.
|
||||
//!
|
||||
//! Declared difference: the R3 owner decision (2026-10-15) gives a trigger without a name of
|
||||
//! its own the opened view's name in each language; the TypeScript renderer wrote the French
|
||||
//! name twice (`svg_compare::TriggerNames`).
|
||||
|
||||
Reference in new issue
Block a user