Issues

Importing a shallow snapshot into a doc with concurrent ops stalls as permanently pending when the snapshot root is a single-head frontier (multi-head root imports fine)

#1040

· vasiliytsykin opened

on Jul 4, 2026

Richtext: expand-after mark absorbs a concurrent insert at its start boundary; undoing the mark leaves style residue on the merged remote text

#1009

· leotumwattana opened

on Jun 11, 2026

Per-container `UndoManager` scope (use case: per-file undo on a unified `LoroDoc`)

#981

· edochi opened

on May 8, 2026

So I did something where I restored an older backed up loro doc - then tried to sync it with devices, it would keep crashing and have no idea how to debug this

#944

· clearly-outsane opened

on Apr 4, 2026

Expose inner LoroDoc reference from loro-wasm::LoroDoc for extension crates

#942

· agronbajraktari opened

on Mar 31, 2026

Storage-backed mode for LoroDoc — compaction without full in-memory materialization?

#940

· agronbajraktari opened

on Mar 30, 2026

UndoManager: redo across separate undo steps loses text when LoroTree node is recreated with new TreeID

#938

· hondrytravis opened

on Mar 29, 2026

Emscripten target uses wrong get_sys_timestamp() path

#934

· 79623798464325 opened

on Mar 21, 2026

LoroTree make public ( on TS ) the children_num function

#930

· feraxhp opened

on Mar 19, 2026

UndoManager "includes" origin prefixes filter

#917

· canadaduane opened

on Feb 14, 2026

undo() returns false for text edits in nested tree containers after importing from independent doc

#915

· the0riginalgandalf opened

on Feb 7, 2026

`forkAt` inside subscription during `checkout` event corrupts document state

#907

· canadaduane opened

on Jan 22, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Importing a shallow snapshot into a doc with concurrent ops stalls as permanently pending when the snapshot root is a single-head frontier (multi-head root imports fine)

Richtext: expand-after mark absorbs a concurrent insert at its start boundary; undoing the mark leaves style residue on the merged remote text

Per-container `UndoManager` scope (use case: per-file undo on a unified `LoroDoc`)

So I did something where I restored an older backed up loro doc - then tried to sync it with devices, it would keep crashing and have no idea how to debug this

Expose inner LoroDoc reference from loro-wasm::LoroDoc for extension crates

Storage-backed mode for LoroDoc — compaction without full in-memory materialization?

UndoManager: redo across separate undo steps loses text when LoroTree node is recreated with new TreeID

Emscripten target uses wrong get_sys_timestamp() path

LoroTree make public ( on TS ) the children_num function

UndoManager "includes" origin prefixes filter

undo() returns false for text edits in nested tree containers after importing from independent doc

`forkAt` inside subscription during `checkout` event corrupts document state

Uh oh!

Uh oh!

Search results