A concurrent style or removeStyle whose range end is anchored after a merge-moved child styled a node that was concurrently inserted at the merged anchor, and it did so on the applying replica only. From <r>abcd</r>, A inserts an empty at index 8 and styles [0,6) while B removes [0,5); after a full sync the carries bold="x" on B alone. The anchor resolves through the moved child, so the boundary redirect from #1309 never fires, and the canStyle version-vector check passes because the interloper is the styling client's own insert. Inserts declared inside a merged-away parent now carry mergedFrom set to the declared parent, and style traversal skips nodes under the merge target that appear after the merge-source tombstone with no merge stamp. Each node is judged by its highest ancestor under the target, so an interloper's descendants are skipped with it. style and removeStyle share one predicate over a precomputed after-tombstone set. A node carrying any mergedFrom fails open: an earlier merge leaves the original source in the stamp under the first-move rule, so stamp equality cannot prove the node was outside the range. cloneElement copies mergedFrom and mergedAt, matching splitText, so the judgment does not depend on application order. This mirrors yorkie-team/yorkie#1928, where the design lives in docs/design/concurrent-merge-split.md §9.4 (Fix 22). Found by the property-based Tree test for #1298 right after #1309 landed - it is the follow-up variant #1309 documented.

Uh oh!

Add property based convergence test on Json.Tree #1298

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions