Story

I’m trying to understand whether this is a broader web UI pattern or something specific to certain environments.

Environment: - macOS (Intel-based) - Chromium browsers (Chrome / Edge) - Web app that streams content incrementally into the DOM (token-by-token style)

Observed behavior: - Text selection appears normal, but copy often returns empty content - Partial selections are especially unreliable - Happens during or shortly after streaming updates - Reproduces across clean sessions and after clearing cache - Blocks workflows that depend on copying generated text

What I’ve ruled out: - Extensions - Cache/session issues - OS-level clipboard permissions

Context: - Support acknowledged it as an unresolved, ongoing reliability issue - No workaround or fix timeline was provided - I’m trying to understand root causes or mitigation patterns rather than complain

Questions: - Have you seen similar copy/paste failures with streamed or incremental rendering? - Known anti-patterns with selection ranges being invalidated by re-renders? - Practical mitigations (buffering, pausing updates on selection, virtualization limits)? - Does this sound more like a Chromium issue or a framework-level one?

Appreciate any pointers or similar experiences.