Verify native input and snapshot isolation during progressive copy
This commit is contained in:
@@ -1015,3 +1015,16 @@ Chrome input, checks mounted-node growth, inserts text and checks DOM identity,
|
||||
focus and content before measuring deep copy. It then clears selection with a
|
||||
native empty-pane click. Reports include `inputCheck.beforeEditing` and
|
||||
`inputCheck.duringEditing`; this preflight is outside the copy timing window.
|
||||
|
||||
Set `HEADLESS_PERFORMANCE_EDIT_DURING_COPY=1` with `--performance` and at least
|
||||
1000 nodes to add a mixed-workload probe. After the first copied frame, it finds
|
||||
an exposed native hit point on the original card, double-clicks it, composes
|
||||
Chinese text and inserts three text chunks while copying. It checks focus/DOM
|
||||
retention, bounded mounted nodes and that input actually overlapped publication.
|
||||
After all ACKs it checks the original's new text and the copy's captured old text
|
||||
separately. No synthetic click passes through an overlapping copied card.
|
||||
`duringCopyInput.samples` records browser input-event time to the second rAF,
|
||||
latest value and retained focus. These frame opportunities exclude time before
|
||||
the browser dispatches the input event; they are not end-to-end key latency or
|
||||
proof that every intermediate composition string reached the display. Mixed
|
||||
workload timings must be kept separate from the no-input copy baseline.
|
||||
|
||||
Reference in New Issue
Block a user