Use the built-in presentation
Pass comments: true to a DOCX or PPTX ScrollViewer to use the built-in margin. The same comments option controls visibility and resolved-thread policy across DOCX, XLSX and PPTX. XLSX keeps its existing default comment presentation.
The default structure is intentionally simple. Applications can adjust its appearance with stable CSS classes and custom properties without recreating the Viewer.
Show DOCX comments
import { DocxScrollViewer } from '@silurus/ooxml/docx';
const viewer = new DocxScrollViewer(container, {
comments: true,
});
await viewer.load(source);Compose a different UI
Applications that need a different structure can use format-scoped comment data and anchor geometry. DOCX resolves comment threads per rendered page, PPTX exposes comments per slide and element bounds, and XLSX exposes comments per sheet plus current-viewport cell rectangles.
This lower-level path leaves framework components, interaction, list virtualization and editing workflows under application ownership.
Word tracked changes
DOCX parsing now retains recorded insertions, deletions and moves from the document body as detached data. The rendered document is the accepted-final state: deletions and move sources do not appear on the page, and there is no built-in tracked-change markup view.
Comments and tracked changes remain separate document concepts and separate public data. The Viewer does not combine them into an editable review model.
Upgrading
No existing option is removed or renamed. DOCX and PPTX comments appear only when enabled, while XLSX preserves its established default. Applications that do not display review information require no changes.
Comments in context
DOCX and PPTX ScrollViewers can place comment cards beside the page or slide, close to the authored location. XLSX viewers retain cell-anchored comment markers and cards. Replies and resolved state are kept when present in the file.
The feature is read-only. Editing, replying, resolving and application-specific review workflows remain the responsibility of the host application.