Repository navigation
HTMLEdit 1.4.1 — Table-of-contents navigation fix
HTMLEdit 1.4.1 — Table-of-contents navigation fix
Clicking a table-of-contents link such as #section in Interact mode could navigate the preview frame to the editor's localhost address, replacing the document with a connection or frame-loading error. HTMLEdit now scrolls to the target inside the document. Switching back to Edit directly keeps that scroll position.
- Supports element IDs, percent-encoded IDs, legacy named anchors and empty/top fragments. Missing targets leave the document open.
- Preserves the document's links when saving. External navigation restrictions and iframe isolation remain in place.
- No review-format, file-path or checkout/apply changes. Documents and notes do not need migration.
Update
npx --yes @woody_s/htmledit@1.4.1 install --agent allUse --agent claude or --agent codex to update one skill. Save your work and reopen the editor in a new session after updating; an already-running server keeps its loaded runtime. Originals, review files and backups are preserved.
Verification
Local build, formatting and 78 unit tests passed. Chrome and Edge passed 10 interaction cases plus two connected-frame API isolation cases. An actual nine-section document was checked in Edge: every table-of-contents link scrolled correctly, and returning to direct editing preserved the current section. The user's private document is not included in the repository.
The platform scope remains unchanged: Windows Chrome/Edge are primary; Linux/macOS remain experimental, with the previously documented manual Safari/native-picker checks outstanding. Publication uses the existing tag-triggered GitHub OIDC trusted-publishing workflow.
Release validation
- Main CI: Windows, Ubuntu 24.04 and macOS 15 passed for commit
92d62cbc19fe9ad598ec7f7aa7ca944b8cfa2410(78 unit tests per platform; 98 Chrome/Edge cases on Windows, 49 Chrome cases on each other platform; package lifecycle checks). - The initial macOS visual comparison differed at two link-edge pixels by 7/255; the measured rendering tolerance is documented in the repository verification record.
- One Ubuntu CI attempt missed the first anchor scroll. The unchanged source passed 20 local Ubuntu repetitions and the Ubuntu CI rerun; the original failed attempt remains available. This was not counted as a first-attempt pass.
- Trusted-publishing workflow is triggered by
v1.4.1. No local npm publish was used.
Published package verification
npm latest is 1.4.1, published by GitHub Actions with OIDC provenance tied to the release tag and exact source commit. Isolated registry installation and CLI startup passed; npm audit signatures verified the registry signature and attestation.
The npm and GitHub tarballs are byte-identical and match SHA256SUMS. SHA-256: 988c92cc4f42f9ccdd052d8bf0c83441907c271ef7ddd5bf844229e0c802764c.