From 5b1121be16b9fef94668595dab5ace97ca2f4d0d Mon Sep 17 00:00:00 2001 From: iris <2+iris@noreply.localhost> Date: Thu, 3 Sep 2026 21:15:15 -0400 Subject: [PATCH] Take the card's tap back off the words, and let the words still be selected Verified on the emulator with all three gestures on an opened peer message: a tap on its words shuts it, a press held past the long-press timeout selects from them, and the tap that puts that selection away does only that. The earlier note in TODO.md saying markdown inside these cards could not be selected was a coordinate error on my part -- the presses were landing in the card's bottom padding, below the last line -- and it is removed rather than carried forward. Co-Authored-By: Claude Opus 5 --- TODO.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/TODO.md b/TODO.md index ab249fe..d7c0f7d 100644 --- a/TODO.md +++ b/TODO.md @@ -13,11 +13,6 @@ one in place when it turns out to need a decision. (`AiAppSelectionColors`), which took the fill from #5B4C73 to #776394 on that surface. Worth confirming this was the complaint rather than a selection that draws *nothing* on the phone. -- [ ] Text inside an opened peer message or memory note cannot be selected at - all — the heading of the same card can, and so can a tool call's output, - so it is the markdown text specifically. Pre-existing (measured against - the build before this session's changes, by stashing them). It - contradicts AGENTS.md's "all transcript text is selectable". - [ ] Messages received from other agents are inconsistent — sometimes they appear, sometimes they don't. **Needs a rig.** Read the code rather than measured: a live Claude session only learns of a peer message from the