odf.js's typed layer has no write-side embedded-sub-document machinery at all -- no writer builds an "Object N/" package, wires its manifest entries, or emits a draw:object reference -- and documents.js's odt/ods editors consequently accept only the 'formula' objectKind, silently omitting wordprocessing, presentation, spreadsheet, and drawing kinds. Since #761 closed the read side of the odt-ods embedding cycle, the write side is now the asymmetric half, and it blocks any workflow that embeds a spreadsheet in a text document.
Evidence
odf.js src/typed/ods/write.ts: "odf.js's typed layer has no write-side embedded-sub-document machinery at all yet (no writer builds an "Object N/" package, wires its manifest entries, or emits a draw:object reference), and building that from scratch is a substantial undertaking of its own." documents.js src/edit/ods/floating.ts:196 states the identical gap for every non-formula objectKind.
Affected packages: odf.js, documents.js
Surfaced by a full-repository gap survey (feature/fidelity/write-support gaps), cross-checked against the existing issue history so it does not duplicate prior work.
odf.js's typed layer has no write-side embedded-sub-document machinery at all -- no writer builds an "Object N/" package, wires its manifest entries, or emits a draw:object reference -- and documents.js's odt/ods editors consequently accept only the 'formula' objectKind, silently omitting wordprocessing, presentation, spreadsheet, and drawing kinds. Since #761 closed the read side of the odt-ods embedding cycle, the write side is now the asymmetric half, and it blocks any workflow that embeds a spreadsheet in a text document.
Evidence
Affected packages:
odf.js,documents.jsSurfaced by a full-repository gap survey (feature/fidelity/write-support gaps), cross-checked against the existing issue history so it does not duplicate prior work.