NEC-324: Obsidian's own canvas stacking reaches the document as a reorder, and two vaults doing it at once keep a conflict copy #316
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
dependencies
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
security
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!316
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-324-obsidians-own-canvas-stacking-reaches-th"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task: NEC-324 — https://projectron.nerchure.com/tasks/344
Obsidian 1.14 loads every canvas card after the first group at zIndex -1 and moves each to the top of the stack as it is first drawn, so panning restacked the board and the next edit carried that in as a reorder of every card drawn since: 14 cards for one colour change, and a conflict copy of the whole board when two vaults did it at once (NEC-314's replay). The live binding now places those unplaced cards in the order the view already shows as it binds, and afterwards only the cards a remote draw or an undo brought in, never a card the user has just made. The fake canvas now stacks as Obsidian 1.14 does, the order-keys log line names its caller, and SAFE-A20 and docs/sync-limitations.md say so. Verified: local gate, seed 1584194348 replay with B on 1.13.7, a fresh canvas hardness hour, two fresh-context reviews. Rides along NEC-335, a race in the markdown-links e2e test (FLAKE-21).
Spec:
docs/changes/NEC-324-canvas-stacking-not-a-reorder/spec.mdAlso fixes NEC-335: markdown-links e2e reads a note's links in a second look after waiting for them, and finds none when the reading view redraws in between
Changelog
Panning across a large canvas no longer restacks its cards in the other vault, or keeps a conflict copy of the board when two vaults are open at once.