Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

<img> wider than its rendering column fails to paint on Android — silently in isolation, with an "invalid measurement" error alongside any other text (not a decode-timing race)

Aperta
  • Qualcosa non va?
#797 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@hejsztynx ci sta già lavorando.

Dal 24/9/2026.

  • #807 di @hejsztynx — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android, react-native
Ambito
mobile

Direzione di ricerca

Inizia da MeasurementStore.measure() e dal percorso delle immagini Android che coinvolge AsyncDrawable e ImageDecoder.setTargetSize. Esegui la riproduzione minima collegata con i tre casi di immagini sovradimensionate, quindi confronta il comportamento della misurazione su una riga e su più righe e il log delle misurazioni non valide. Il lavoro è completato quando le immagini sovradimensionate non falliscono più silenziosamente né scompaiono durante il rendering.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

Describes the bug

An <img> tag whose declared width exceeds the actual width of the column EnrichedText renders it into fails to paint on Android. This is fully deterministic — not a timing race — and reproduces on the very first cold launch, every time.

I originally filed this issue theorizing an unsynchronized bounds race in AsyncDrawable (ImageDecoder.setTargetSize reading a still-zero Rect before the text-layout pass assigns real bounds). That was a plausible read of the source, but after extensive testing (cold cache, warm cache, a local low-latency image server, and the exact resolve-then-remount sequence a real consuming app uses, run concurrently across 16 images) I was never able to reproduce it. Everything I've actually observed — including the original production bug that led me to file this — is fully explained by the mechanism below instead, with no timing element at all. Retracting that theory.

The failure takes two different shapes depending on context:

  1. The <img> is the only content in the EnrichedText — the failure is completely silent. No exception, no broken-image placeholder, nothing logged anywhere.
  2. There's any other text in the same EnrichedText (true of essentially all real admin-authored content — headings, paragraphs, etc. around an image) — the same failure now logs a concrete diagnostic: 
    ReactNativeJNI: EnrichedTextView returned an invalid measurement. Min: [0,0] Max: [384,inf] Actual: [400,404.333]
    Max is the real available column width; Actual is what the measure function reported back, driven by the embedded image's declared size.

This split traces to MeasurementStore.measure(): single-line content reports StaticLayout.getLineWidth(0), but multi-line content reports StaticLayout.width instead — and that can still exceed the nominal wrap width when one line contains an unsplittable inline image wider than the rest.

To Reproduce

Minimal repro app: https://github.com/ekrapfl/rne-html-repro-android-img-paint

  1. npm install && npm run android (native dev build, Fabric).
  2. Three cases render: an image that fits (paints normally), the same image declared far wider than the screen with no other content (renders at full size, overflowing the screen edge uncropped), and that same oversized image with a paragraph before it (reserves no visible space, shows nothing).
  3. adb logcat | grep -i "invalid measurement" around the third case.

Expected behavior

An oversized declared width shouldn't cause total, silent render failure. At minimum, a diagnostic should surface consistently (right now it only does when there's other text in the same view); ideally the library would clamp/scale the image to the available column itself, the way a browser does with img { max-width: 100% }, rather than leaving every consumer to compute and inject a safe pixel width themselves.

Device tested

  • Pixel 10 Pro XL emulator (sdk_gphone16k_arm64), Android API 37
  • react-native-enriched-html 1.1.1, React Native 0.86.3, Expo ~57.0.23, Fabric (New Architecture)

Additional context

One honest caveat: the visual failure reproduces reliably in the minimal repro above, on a fresh cold install, every time. The exact JNI log line was confirmed repeatedly against a full production app under a matching layout structure, but hasn't fired in the standalone repro despite matching nesting depth, padding, and styling — something about the fuller app context matters there that I haven't isolated. The visual symptom (reserves no space, never paints) is the same failure either way.

Lingua principale
C
Stelle
1.4k
Fork
68
Merge medio
3g 16h
PR unite (30g)
6

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di software-mansion/react-native-enriched-html

Tutte le issue di software-mansion/react-native-enriched-html

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.