Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Text immediately before an `<img>` sometimes fails to repaint on iOS after a screen revisit (`EnrichedText`)

Abierto
  • ¿Algo no está bien?
#798 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

@hejsztynx ya está trabajando en esto.

Desde el 22/9/2026.

  • #804 de @hejsztynx — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
ios, objective-c, react-native
Área
mobile

Línea de trabajo

Empieza en EnrichedTextView.mm, especialmente en renderContent, y compara el manejo de textStorage y layout con EnrichedTextInputView.mm y _performRelayout. Reproduce el problema mediante expo-router o React Navigation con react-native-screens, saliendo de la pantalla y volviendo a ella en iOS. Se considera terminado cuando el texto inmediatamente anterior a un se pinta de forma consistente en las visitas posteriores sin regresiones en el renderizado inicial.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

Describe the bug
When EnrichedText renders HTML containing an <img>, the text on the line immediately before that image can fail to visually paint on iOS. The text is still present and correctly positioned (confirmed via the accessibility tree), but it never gets drawn. The rest of the surrounding content renders fine.

This issue is specifically correlated with revisiting a screen via React Navigation (@react-navigation/native + react-native-screens native-stack, via expo-router). A fresh first visit renders correctly, but navigating away and then back causes the line to reliably or intermittently fail to paint. This is an iOS-only issue and does not reproduce on Android.

Investigation ruled out JS-side remount timing issues (the bug persists even with zero remounts/key changes on revisit, or when forcing fixed-delay remounts).

To Reproduce
Steps to reproduce the behavior:

  1. In an app using expo-router or @react-navigation/native (with react-native-screens), create a screen that renders EnrichedText.
  2. Provide HTML ending in a text block immediately followed by an <img>, e.g., ...<div>Some text</div><img src="..." width="..." height="..." />.
  3. Navigate to that screen. (Observe that it renders correctly).
  4. Navigate back to the previous screen.
  5. Navigate forward to the same screen again.
  6. See error: The line of text immediately before the <img> is now blank (though still present and correctly positioned in the accessibility tree).

Expected behavior
The text immediately preceding the <img> tag should consistently paint and remain visible on subsequent visits to the screen, mirroring the behavior of the initial visit.

Screenshots
(Not applicable/No screenshot provided — visually, it manifests as empty space where the text should be).

Device (please complete the following information):

  • Device: iPhone 17 Pro (iOS Simulator)
  • OS: iOS 26.4
  • Version: react-native-enriched-html v1.1.1 (Running on React Native 0.86.3, Expo ~57.0.20, Fabric new architecture)

Additional context
Reproduction context: This issue could not be reproduced in isolation (e.g., via a Storybook story with identical HTML and remount behavior). It strictly depends on real React Navigation transition/view-controller behavior.

Potential contributing factor identified: In EnrichedTextView.mm, renderContent fully rebuilds textView.textStorage on every render but never explicitly invalidates/re-lays-out the NSLayoutManager around the changed content. This contrasts with the editable EnrichedTextInputView.mm, which works around similar TextKit gaps via _performRelayout. Patching EnrichedTextView to mirror this sequence did not reliably fix this specific bug on its own, but it highlights a potential TextKit gap.

Questions for maintainers:

  • Is there a known interaction between EnrichedTextView's render/layout cycle and view controller appearance/reappearance (e.g., viewWillAppear/native view recycling) that could cause a stale/incomplete TextKit layout pass specifically on a view's second-or-later appearance in a navigation stack?
  • Are there any existing instrumentation or debug flags in the library for tracing NSLayoutManager invalidation timing to help build a tighter reproduction?
Lenguaje dominante
C
Estrellas
1.4k
Forks
67
Merge medio
3 d 22 h
PR fusionados (30 d)
8

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de software-mansion/react-native-enriched-html

Todos los issues de software-mansion/react-native-enriched-html

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.