• a16901d: Respect margin properties passed via dragImageProperties on the drag preview. The clone reset its margin to 0 after copying styles, which discarded any margin the user explicitly requested. The reset now runs only when no margin property is listed in dragImageProperties, so the drag image can keep the same spacing as the live block.
• @tiptap/core@3.27.1
  • @tiptap/extension-collaboration@3.27.1
  • @tiptap/extension-node-range@3.27.1
  • @tiptap/pm@3.27.1

• a16901d: Fix ordered list parsing so under-indented continuation lines preserve their first character.
• @tiptap/core@3.27.1
  • @tiptap/pm@3.27.1

• a16901d: Fix Placeholder flickering while a modal overlay is open. When the editor was occluded during a stream of transactions (e.g. remote collaboration edits), the viewport measurement fell back to a full-document range and repeatedly toggled the data-placeholder attribute on empty blocks. The viewport window is now frozen when the editor can't be measured reliably, so placeholders stay stable.
• @tiptap/core@3.27.1
  • @tiptap/pm@3.27.1

• Updated dependencies [6047f84]
  • @eigenpal/docx-editor-core@1.8.1
  • @eigenpal/docx-editor-agents@1.8.1
  • @eigenpal/docx-editor-i18n@1.8.1

• @eigenpal/docx-editor-vue@1.8.1

• Updated dependencies [6047f84]
  • @eigenpal/docx-editor-core@1.8.1
  • @eigenpal/docx-editor-agents@1.8.1
  • @eigenpal/docx-editor-i18n@1.8.1

• 6047f84: Emit word/numbering.xml when exporting documents whose lists have no original numbering part

  createDocx() (and any export of a document built from scratch — e.g. the editor with no source .docx) wrote <w:numPr w:numId=…> onto list paragraphs but never generated the backing word/numbering.xml, nor its content-type override / document relationship. Word couldn't resolve the dangling numIds, so it silently dropped every bullet and number marker — ordered/bulleted lists opened with no markers.

  fromProseDoc now reconstructs the numbering definitions from the editor's list state (the list attrs were previously discarded on the no-base path), and the repacker serializes them to word/numbering.xml — registering the content-type override and relationship — when the package doesn't already ship one. Documents that already contain a numbering.xml are passed through unchanged.

See the changelog for release notes: https://github.com/remix-run/react-router/blob/main/CHANGELOG.md#v801

• 274e45f: applyReview now reports when a batch accept/reject id is note-resident. An id that lives only inside a footnote or endnote previously surfaced as a bare "Tracked change not found", giving no hint the id exists but isn't body-mutable here. It now returns a message saying the change is inside a footnote/endnote and must be resolved through the note-targeting accept/reject API. Batch ids stay document-body-scoped — this sharpens the error only and is fully backward-compatible (the new note stores are passed internally and optional).