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 bdeb0b2
Browse filesBrowse the repository at this point in the historyBrowse files
Keep unreleased strokes and buttons under the physical-input lock, preserve uncertain host recovery, and refuse unsafe fallback or disposal. Fix Windows portability of desktop-test lifecycle and reporting contracts.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 53a0c7cf-1330-4677-8700-d249b508c6ee
Copy file name to clipboardExpand all lines: .changeset/win-helper-cancellation.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,4 @@
2
2
'@fluentui-react-native/desktop-driver': patch
3
3
---
4
4
5
-
Check cancellation in more Windows helper waits: bounded UI Automation calls, the whole-subtree cache, window response probes, posted window restores and moves, activation retries, and the `closeApplication` termination wait, and a cancelled mutation reports effect `unknown`. Direct UI Automation calls and the activation calls themselves can still block. Window management and activation probe the target window first and fail with reason `target-non-response` when it does not answer. A restore that stalls after its initial probe reports effect `unknown` rather than `partial`. Held keys and buttons keep the physical input lock until released, and queued commands are dropped after the transport ends. A malformed or non-object JSON frame now fails the transport. Pointer presses and scrolls over another application's window are refused, failed pattern and focus reads are no longer reported as unsupported or unfocused, a job-contained launch root is no longer terminated after launch, a packaged launch root must report its AUMID, an unreadable start time fails the lease, and activation grants foreground rights only to the target process.
5
+
Check cancellation in more Windows helper waits: bounded UI Automation calls, the whole-subtree cache, window response probes, posted window restores and moves, activation retries, and the `closeApplication` termination wait, and a cancelled mutation reports effect `unknown`. Direct UI Automation calls and the activation calls themselves can still block. Window management and activation probe the target window first and fail with reason `target-non-response` when it does not answer. A restore that stalls after its initial probe reports effect `unknown` rather than `partial`. Held keys and buttons keep the physical input lock while the helper runs; failed cleanup retains unreleased input for retry, and a failed physical mutation reports an unknown effect. The adapter retains uncertain input for recovery, and disposal reports failed cleanup. Queued commands are dropped after the transport ends. A malformed or non-object JSON frame now fails the transport. Pointer presses and scrolls over another application's window are refused, failed pattern and focus reads are no longer reported as unsupported or unfocused, a job-contained launch root is no longer terminated after launch, a packaged launch root must report its AUMID, an unreadable start time fails the lease, and activation grants foreground rights only to the target process.
0 commit comments