DWAA1660andClaude Opus 5.5 9fa837e452 Issue #173: a failed ?file= startup fetch is reported in the app (#302) ...

When the browser app's `?file=` URL couldn't be fetched (an HTTP 404, a
network or CORS failure), the error went only to the developer console and
the user saw the ordinary welcome screen with no sign the PDF was tried.

The fetch now also queues `(name, error)` in a new `failed_inbox` next to
the existing `inbox`, and the app reports it on the next frame with the
notice it already uses for a delivered file that won't open: "Couldn't open
missing.pdf: HTTP 404". The console line stays for developers.

Test: a_failed_startup_url_is_reported_in_the_app (pickers.rs).


Claude-Session: https://claude.ai/code/session_01K3vVft4VXvvy8SpbbUceTW

Co-authored-by: Claude Opus 5.5 <[email protected]>

2026-10-08 12:49:25 -04:00

..

pdfcraft

Desktop: no eprintln! on the log and panic paths (#246)

2026-10-08 07:03:03 -04:00

pdfcraft-cli

CLI text tests: each protected-PDF test writes its own files (#267)

2026-10-08 08:33:26 -04:00

pdfcraft-web

Issue #173: a failed ?file= startup fetch is reported in the app (#302)

2026-10-08 12:49:25 -04:00