1.0.5 — Match DOM nodes to .canvas JSON by element order

Fix (Advanced Canvas compatibility): nodes in the DOM did not carry data-id, so the 1.0.4 fallback never matched.

Change: read .canvas JSON and map each .canvas-node element to the nodes[] entry at the same DOM order index (Canvas and Advanced Canvas render nodes in JSON order). When a DOM element does carry data-id, that mapping wins.

Effect: text folded by low zoom or small node size is now restored from the original markdown and re-rendered into the cloned snapshot.

1.0.4 — Restore full node text from .canvas JSON

Fix: nodes with folded/truncated text in DOM (caused by low zoom or small node size in Canvas / Advanced Canvas) now display their full content in the exported HTML/PDF.

What changed:

• Read the current .canvas file's JSON to build a data-id → text map.
• After cloning each node, replace its inner content with the original markdown re-rendered via MarkdownRenderer, so the exported PDF always shows the full text even when the live editor has folded it.

No other behavior changes. Upgrade from 1.0.3 by reinstalling the plugin in Obsidian (Community Plugins → Canvas Live Snapshot → Reinstall, or download the three release assets and replace files in .obsidian/plugins/canvas-live-snapshot/).

1.0.3 — Attestation workflow enabled

Re-publish to trigger an Obsidian community review that picks up the new artifact attestations generated by the .github/workflows/attest.yml workflow.

This release has no functional changes from 1.0.2 — it only bumps the manifest version. The release assets main.js, manifest.json, and styles.css are all signed by GitHub Actions via actions/attest-build-provenance@v1 immediately after publication.

1.0.2 — Canvas snapshots with automatic opening

Export the rendered canvas to an HTML snapshot, save it to the system Downloads directory, and open it automatically with the default HTML application. Includes configurable margins, timestamped filenames, collision-safe saving and separate error handling for saving and opening. PDF output is produced through the browser's print dialog. Desktop only. See the README for rendering and embedded-page limitations.