mirror of
https://github.com/getpaseo/paseo.git
synced 2026-10-31 21:52:54 +00:00
Mohamed Boudra
0474c3e0af
The mock provider splits "**Bold" into two frames, "**Bo" and "ld". The helper forwarded both back-to-back and asserted the strong span reads "Bold", which only holds when the browser commits both frames to the store in one reducer flush and the message first mounts with "**Bold". When a frame boundary lands between the two tasks the message mounts with "**Bo" and word pacing holds "ld" until the whitespace after it arrives, so the span reads "Bo" until the gate releases. That is the designed behaviour of the reveal, and the batching is up to the browser's task scheduling. Stop after "**Bold text" instead: the space after "Bold" ends the word, so every batching reveals "Bold" and never more than "text". Forcing the frames into separate commits reproduced the CI failure before the change and passes after it.