Repository navigation
Android: native render errors, low-memory exits, and inline WebView taps blanking the feed #62
Description
Observed
- 2026-11-01 read-only diagnosis of the S25: repeated native view-removal and text-overflow errors in the T3 Android logs, plus background low-memory exits. It was never reproduced and no fix was made. The thread stalled during a recording window.
- In the OpenUI lab build, tapping inside an inline
html_renderWebView blanks the feed until the user scrolls. So far it was only seen on an agent-owned virtual display. - Related, closed upstream:
16989(inline HTML traps scrolling).
Plan
- Capture
adb logcatforcom.t3tools.t3codeduring a normal session and group the errors by stack. - Reproduce the WebView blank on the main display, with stock and lab builds side by side.
- File focused fixes or upstream reports per root cause. Check upstream main first, since the owner runs 0.1.2.
Acceptance
- Each error class is either explained with a repro or shown to be fixed on current upstream.
- WebView tap no longer blanks the feed (also tracked in UX wave: T3 Code daily-driver fixes + generative UI everywhere (prioritized) #57). Harness artifact; see comment.
Activity
kvnloo commentedon Nov 2, 2026
Update: the "inline WebView taps blank the feed" item was a test-harness artifact, not an app bug. The run that reported it drove the lab app on a 1080x2340/420 virtual display while the phone's main display was 1440x3120/560. That mismatch also mis-measured text and misplaced taps. With matched geometry, a live
html_rendertreemap on the lab build took Open and Back taps inline and the feed stayed intact. I'm ticking that checkbox. The logcat items (view removal, text overflow, low-memory exits) are still open.