Web client: the chat behind a sheet ends 258 px short of the bottom when the site loads fast
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, swift
Research direction
Start with the snapshot harness's web-mobile models screen and compare runs 927 and 956, then trace how the Claude Code sheet is presented and how the chat transcript is sized or scrolled as attachments load. The issue points to AgentUI's TranscriptView or Isomer's web ScrollView, but names no files or tests. Done when the screen matches across both serving setups, with the transcript pinned at the bottom or the fixture waiting for attachments before showing the sheet.
Written by the indexing model from the issue text.
Description
Found by the snapshot harness's web-mobile models screen: the fixture's chat with the Claude Code sheet (Approval, Model) over it, in Mobile Safari on an iPhone 17 Pro simulator. Only this screen differs; the other ten are the same either way.
The two states, each stable (the harness's second look agrees):
- Site served from the Mac, across the VMs' network (blue-ios on the old runner, run 927): the chat behind the sheet is at the bottom. The
/goalmessage and the top of "Goal set" sit just above the sheet, where thechatscreen (no sheet) has them. - Site served on the simulator's own VM, on its loopback (blue-ios on visor-jit via a Mac slot, run 956; and the reference before #221): the chat sits 258 px short of the bottom. "Here's the layout I want for the offline banner." is the last row above the sheet. 258 px is about the height of the row with the picture and
banner.mov.
So it depends on timing. A plausible reading: when the attachments' row gets its height before or after the sheet is presented, the transcript under the sheet is or isn't kept pinned to the bottom. Where that pinning lives (AgentUI's TranscriptView or Isomer's ScrollView on the web) is to be found.
For now: the reference follows where CI serves the site. #221 re-recorded it for the Mac-served state; #226, which moves blue-ios to visor-jit, records the loopback-served one.
Done when: the screen comes out the same whichever way the site is served. Either the transcript under a sheet stays at the bottom as its rows load (as the chat screen does), or the fixture waits for the attachments before presenting the sheet.
🤖 Generated with Claude Code
- Dominant language
- Swift
- Stars
- 1
- Forks
- 0
- Avg merge
- 7h 43m
- Merged PRs (30d)
- 131
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AttilaTheFun/visor
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AttilaTheFun/visor#244 ·
Maintainers usually reply within 1 day
-
Mac: opening the inspector on a narrow screen loops the split view's layout, then crashesPossibly taken @logan-shire-claude claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
AttilaTheFun/visor#240 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 35/100
AttilaTheFun/visor#210 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
AttilaTheFun/visor#164 ·
Maintainers usually reply within 1 day
All issues in AttilaTheFun/visor
Similar issues
-
feat: 앱 정보에 개인정보처리방침과 고객지원 연결Possibly taken @xrpjwk8 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
DeveloperAcademy-POSTECH/2026-C6-A13-Hear-I-am#120 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
swiftlang/swift-java#955 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
michaelnisi/hanstholm#246 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
deepsealabs/libdc-swift#110 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
jaywcjlove/quick-rss#448 ·