You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4b0d146
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ios-runner): bound the synthesized replacement pace so a value-owning field keeps it
A replacement burst typed at XCTest's default 60 characters/second outruns an app
that owns its field's value and re-applies it after the edit that produced it, which
is how a controlled React Native `TextInput` behaves. That write erases whatever the
burst typed while it was in flight and the field then sits stable short of the
request: first characters and tail survive, a middle run is gone, which is the
`fill id="field-email" ada@example` -> `aexample` CI signature. The commit wait can
refuse such a value but cannot repair it, because a retype races the same write.
12 characters/second spaces characters ~83 ms apart. The new
`--agent-device-text-entry-async-value-write` fixture owns its field's value and the
iOS lane test pins the pace against it: raising the pace re-opens the race and turns
that test red. A write-back still in flight 150 ms after an edit corrupts a burst at
this pace too, so this narrows the window rather than closing it, and the measured
wall-clock cost of the pace is recorded next to the commit ceiling it sits upstream
of.
Closes#2080
0 commit comments