From 8eb3e1a6db3c619e2ef129da76708b5da31571fa Mon Sep 17 00:00:00 2001 From: vanelsas <58037137+avanelsas@users.noreply.github.com> Date: Tue, 12 May 2026 19:33:56 +0200 Subject: [PATCH] Release v0.6.0 Co-Authored-By: Claude Opus 4.7 (1M context) --- CHANGELOG.md | 107 +++++++++++++++++++++++++++++++++++++++++++++++++++ package.json | 2 +- 2 files changed, 108 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 758ad46..640e677 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,6 +10,113 @@ possible" — I won't promise API stability until `1.0.0` lands. Nothing yet. +## [0.6.0] — 2026-05-12 + +A bug-fix + audit-driven internal-refactor pass on top of BareDOM +3.0.0. No new user-facing features; the visible work is six bug +fixes the maintainer surfaced from smoke testing, and the bulk +of the diff is an audit sweep that leaves the codebase noticeably +closer to its own stated design rules. + +### Fixed + +- **Inspector Escape erased bound text.** Pressing Escape inside + any `x-search-field`-backed inspector input (text attributes, + layout fields, name, CSS-var editors, seed cells, bind pickers) + silently committed an empty string to the doc. Browsers treat + Escape on `` as a clear gesture and fire + an `input` event with the cleared value, which the inspector + then committed. Every inspector `x-search-field` now intercepts + `keydown` and suppresses Escape's default behaviour. +- **`x-select` pickers painted blank.** Placement, single-select + enum, and multi-select shared-attribute pickers showed no value + even when a stored attribute existed. BareDOM's x-select renders + from the host's `value` attribute, not from a slotted + `