From cd2e4cfaf3b01103db6b9497a1ea7068c08e8be7 Mon Sep 17 00:00:00 2001 From: GenericJam Date: Sat, 4 Jul 2026 22:07:06 -0600 Subject: [PATCH] changelog: stage 0.7.16 doc entries (#63, #64) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Records the two merged doc-only PRs under a new [0.7.16] section so they're ready for the next release (doc changes only reach hexdocs via a publish). No mix.exs bump — this stages the entry without triggering release.yml. Co-Authored-By: Claude Opus 4.8 (1M context) --- CHANGELOG.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 81a0995a..3c3fe87e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,6 +8,21 @@ Full module documentation: [hexdocs.pm/mob](https://hexdocs.pm/mob). --- +## [0.7.16] - 2026-07-04 + +### Documentation +- **Fixed the "first screen" example in the Getting Started guide.** The button + called an undefined `tap(:increment)` helper (there is no render-tree `tap/1`; + only the `Mob.Test.tap/2` desktop helper). It now uses the real idiom + `on_tap={{self(), :increment}}`, which sends `{:tap, :increment}` to the + screen's `handle_info/2` — matching the example's own clause. (closes #46, #63) +- **Made the raw color format explicit: `0xAARRGGBB` integers, not CSS hex.** The + Components and Theming guides now spell out that a raw color prop is a 32-bit + integer with **alpha first** (e.g. `0xFF2196F3`) — not a `"#RRGGBB"` string, + and not CSS's alpha-last `#RRGGBBAA` — and that a missing alpha byte (a 6-digit + `0x2196F3`, read as `0x002196F3`) renders fully transparent. Includes a + translucent-overlay example and notes `:transparent` is `0x00000000`. (#64) + ## [0.7.15] - 2026-07-04 ### Added