Mohamed Boudra
5715b5ba62
The selectable UIKit text view was a sibling of the Fabric content container, so existing chat rows kept an old width after Explorer changed the available pane. Make the container own the text view and preserve layout notifications on bounds changes. Includes a native geometry regression.
1.4 KiB
Native iOS text geometry regression
Run on the Namespace Mac with a fresh simulator development build. Use the PID
returned by xcrun simctl launch <your-task-simulator-UDID> sh.paseo.debug.
Attach only to your task's app, while no device replay is running:
PASEO_NATIVE_TEXT_REFLOW_PID=12345 \
PASEO_NATIVE_TEXT_REFLOW_LOG=/Volumes/devbox/workspace/native-text-reflow.log \
bash packages/app/e2e/mobile/native-text-reflow/ios.sh
The probe constructs the installed RNUITextView, fills its real UIKit text view,
and resizes its content container from 500 to 240 and back to 500 points. It
asserts the inner frame follows both widths and the same selection survives.
It uses public UIView/UITextView operations, without mocking React Native.
LLDB detaches after the probe. An assertion failure or evaluation error fails the
shell command; the log distinguishes them.
This covers native container resizing and selection retention. It does not cover Fabric event delivery, chat row height, reader anchoring, or the on-screen copy menu. Those require the real chat journey: read an older multiline response, open/close Explorer, resize/rotate, inspect complete paragraphs and bullets, retain expanded/collapsed details, and check a stationary reader's position. Accessibility exposes full text even when glyphs are clipped, so a text wait alone does not verify that journey.