Skip to content

Add application-only website parsing and prefilled failure issues - #154

Merged
maebli merged 3 commits into
mainfrom
feat/web-application-fallback
Sep 28, 2026
Merged

maebli merged 3 commits into
mainfrom
feat/web-application-fallback

Conversation

@maebli

@maebli maebli commented Sep 28, 2026 •

Copy link
Copy Markdown
Owner

Application-only payloads such as 78 03 13 15 31 00 and bare DIF/VIF records such as 03 13 15 31 00 now parse on the website after wired and wireless frame detection fails. The fallback supports all website output formats, labels application-only results, and rejects malformed or incomplete records. Existing full-frame APIs keep their strict behavior.

Parse failures and partial frame results show an Open GitHub issue link prefilled with the captured payload, error codes/messages, parse attempts, parser version, output format, browser, and reproduction URL. AES keys are omitted. The toolbar report action uses the captured failure even if the input is edited afterward; successful retries clear stale reports.

Validation:

  • Workspace tests with decryption enabled passed.
  • Application/output contract tests, formatting, and Clippy passed.
  • Release WASM build and actual WASM/inline website-helper integration passed for all seven website formats.
  • Chromium checks verified URL auto-parsing, application-only JSON, bare-record hex view, and the prefilled issue link.
  • Added WASM browser regression tests. Local headless Firefox could not start because its installation encountered permission errors; these tests run in the existing Firefox CI job.

Pages continues to rebuild the WASM assets during deployment.

@maebli
maebli merged commit 3a120c7 into main Sep 28, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant