HTMLEdit 1.5.1 — Safari editing and reliable save/copy

HTMLEdit 1.5.1 — Safari editing and reliable save/copy

Safari can now select document elements and open the inline text editor while keeping document scripts disabled. The fixes preserve 1.5.0 multi-selection, immediate batch deletion and joint notes.

• Use a parent-owned event surface when Safari blocks listeners in the sandboxed preview; keep Ctrl/Cmd selection, Delete and one-step undo/redo working without duplicate keyboard handling.
• Start clipboard permission handling during the click gesture and provide the AI request only after saving succeeds. Failed saves and conflicts preserve the previous clipboard.
• Correct Home/End scrolling in Safari and retain nested scrolling, note-marker positioning and responsive-width previews.
• Preserve review v1/v2, target IDs and joint-note metadata. No review-format migration is required.

Verification

The integrated candidate passed 86 unit tests on Windows, Ubuntu WSL2 and macOS; 132 Windows Chrome/Edge browser cases; and 66 Chrome cases on each of Ubuntu and macOS. Package lifecycle checks and formatting passed.

On the physical Mac, actual Safari 18.6 passed multi-selection, batch delete/undo/redo, joint-note save/reopen, clipboard and download, image editing, scrolling and controlled save-failure/conflict checks. Actual Claude followed the installed skill's checkout/apply procedure in WSLg Chrome, Mac Chrome and Safari, preserving both joint targets and verifying backups and automatic refresh. See the integration record for hashes, environment versions and evidence limits.

Earlier manual tests separately confirmed Safari click/double-click and Korean IME input/apply in Safari and WSLg. WSL required IBus Hangul configuration. Native picker checks were historical and were not repeated for this patch; picker code is unchanged. Windows Chrome/Edge remain primary, with other platform claims limited to the recorded environments.

Update

Run outside the HTMLEdit source checkout:

npx --yes @woody_s/htmledit@1.5.1 install --agent all

Save work and stop/reopen old editor sessions to load the new runtime. Existing skills and already-running servers are not automatically replaced. Documents and backups are preserved. Use --agent claude or --agent codex to update one skill.

Publication follows main CI, then tag v1.5.1, then GitHub Actions OIDC trusted publishing. No local npm publish is used.

Publication verification

• Source: c4fef7f5739bfa834bd072be0226d2118d93afa3.
• Main CI passed on Windows, Ubuntu 24.04 and macOS 15 before tag push: 86 unit tests per OS, 132 Windows Chrome/Edge cases, 66 Chrome cases each on Ubuntu/macOS, plus package lifecycle checks.
• Release workflow passed using GitHub OIDC trusted publishing; npm publisher is GitHub Actions.
• Public npm version and latest: 1.5.1.
• The npm and GitHub tarballs are byte-identical and match the attached SHA256SUMS.
• SHA-256: 67fa19e01d2a2c12c34a742a597132b10ba9588f27b160458531489cfee88749.
• Provenance matches tag v1.5.1, .github/workflows/release.yml and the source commit above.
• A fresh isolated public-registry installation passed both skill installations and a v2 joint-note status → checkout → apply → status smoke, preserving both target IDs, original bytes and exact backup bytes. This is a deterministic publication smoke, separate from the actual Claude candidate verification described above.
• npm audit signatures: one verified registry signature and one verified attestation. A separate npm cache was used after initial stale registry metadata delayed discovery of the new version.

Existing user skill installations and running editor sessions were preserved. Update and reopen as described above to load 1.5.1.