fix(pdf): verify export and offer open PDF and containing-folder actions #23

New Issue

2026-10-11T12:36:16Z

KofTwentyTwo commented

2026-10-11 12:36:16 +00:00

(Migrated from github.com)

Owner reports that Save PDF may not have worked in the running development build and requests options to open the created PDF and/or its folder.

Acceptance:

Reproduce the actual save-picker/export outcome, distinguish cancellation from failure and verify the final PDF exists and is readable.
Preserve explicit user-chosen literal destinations, Unicode/special characters, print settings and document/source/find/collapse/zoom state.
Only after successful creation offer separate Open PDF and Open containing folder actions (the user may use either/both); use the native PDF/default folder handler and handle unavailable handlers/errors clearly.
Do not open or label stale/partial output as a newly successful PDF, and do not auto-submit any physical print job.
Verify actual generated content and success-only actions in native/published and installed channels, retaining build/style/coverage gates.

Related: #12 and the system-print bug. Current-head cause and actual export result are still under investigation; earlier hosted PDF evidence is not proof of this reported attempt.

Substantial AI assistance: Codex (GPT-6).

Owner reports that Save PDF may not have worked in the running development build and requests options to open the created PDF and/or its folder. Acceptance: - Reproduce the actual save-picker/export outcome, distinguish cancellation from failure and verify the final PDF exists and is readable. - Preserve explicit user-chosen literal destinations, Unicode/special characters, print settings and document/source/find/collapse/zoom state. - Only after successful creation offer separate Open PDF and Open containing folder actions (the user may use either/both); use the native PDF/default folder handler and handle unavailable handlers/errors clearly. - Do not open or label stale/partial output as a newly successful PDF, and do not auto-submit any physical print job. - Verify actual generated content and success-only actions in native/published and installed channels, retaining build/style/coverage gates. Related: #12 and the system-print bug. Current-head cause and actual export result are still under investigation; earlier hosted PDF evidence is not proof of this reported attempt. Substantial AI assistance: Codex (GPT-6).

KofTwentyTwo commented

2026-10-11 12:59:17 +00:00

(Migrated from github.com)

Implemented locally: opt-in Open PDF after saving and Open containing folder after saving; either/both can be selected. Export must succeed and Windows’ PDF loader must read pages before success/actions. Viewer/folder handler failures are independent and cannot relabel a completed export as failed. Selection/export phase diagnostics retain no private paths. Release build passes; existing real-PDF cases compile with the updated path, but no new PDF/post-action runtime result exists. The owner’s exact export outcome and desktop reservation questions remain pending. Ticket stays open.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: KofTwentyTwo/MarkdownViewr.Windows#23