iris bench: a press only reaches what the pointer is on (ai-app-2 5e34dba)
Iris's report on the previous bench build: a vertical scroll locked to a horizontal scroll area whose fling was still running, and the message box clipping its text 12dp inside its own edge.
This commit is contained in:
1 parent
00784d924e
commit
174ca31067
2 files changed
+29
No files matched your search
@@ -11,6 +11,35 @@ no enrolment and no permissions.
|
|||||||
|
|
||||||
The rest of this file is the runbook that was delivered with the APKs.
|
The rest of this file is the runbook that was delivered with the APKs.
|
||||||
|
|
||||||
|
**2026-09-08 (later still): the scroll lock, and the input box's clip.**
|
||||||
|
`iris-bench-arm64.apk` rebuilt from ai-app-2 `5e34dba`. Both are from
|
||||||
|
your report on the bench build, and both have a test that fails without
|
||||||
|
the change.
|
||||||
|
|
||||||
|
- **"If I try to scroll vertically while a horizontal scroll animation
|
||||||
|
is still active, it stays locked to the horizontal scroll."** Your
|
||||||
|
diagnosis was the right one: it was global state, and the fling had
|
||||||
|
nothing to do with it. A widget kept receiving presses for one frame
|
||||||
|
*after* the finger left it (the frame that exists so a hover can end),
|
||||||
|
and a press landing on something that is already coasting commits to a
|
||||||
|
pan immediately, with no slop -- so a code fence grabbed the whole
|
||||||
|
gesture from wherever on the screen you actually touched. Measured
|
||||||
|
before the fix: a finger put down 500px above a coasting fence and
|
||||||
|
dragged 160px down the screen moved the list by nothing at all. A
|
||||||
|
press now only reaches the widget it is actually on. What to try:
|
||||||
|
flick a code block sideways and, while it is still moving, scroll the
|
||||||
|
transcript up and down somewhere else -- the transcript should follow
|
||||||
|
your finger and the code block should carry on coasting on its own.
|
||||||
|
Putting a finger down *on* the coasting block still catches it,
|
||||||
|
whichever way you then drag, which is what Compose does.
|
||||||
|
- **"The message input box doesn't clip correctly."** It was clipped 12dp
|
||||||
|
inside its own edge, so a long message was sliced through the middle of
|
||||||
|
a line of text with a band of bare grey above the cut. The box itself
|
||||||
|
is the clip now -- the same rounded rect that draws the bar is what the
|
||||||
|
text is cut to, so text disappears under its edge. The padding still
|
||||||
|
holds the text off the edge at the end you are typing at. What to try:
|
||||||
|
type or paste more than six lines and scroll inside the box.
|
||||||
|
|
||||||
**2026-09-08 (late): the four defects from your second report.**
|
**2026-09-08 (late): the four defects from your second report.**
|
||||||
`iris-bench-arm64.apk` rebuilt from ai-app-2 `a2e5e58`. Everything here
|
`iris-bench-arm64.apk` rebuilt from ai-app-2 `a2e5e58`. Everything here
|
||||||
comes from the report you sent, and each one has a test that fails
|
comes from the report you sent, and each one has a test that fails
|
||||||
|
|||||||
Binary file not shown.
Reference in new issue
Block a user