Record bounded preactivation focus capture observation

This commit is contained in:
Joseph Doherty
2026-11-14 00:17:52 -05:00
parent 1d251d7e3c
commit 78b95cab08
2 changed files with 65 additions and 0 deletions
@@ -32,3 +32,9 @@ python3 infra/tools/ui-consistency/check_dialog_focus_recovery.py --output docs/
```
This is native adapter behavior, not manual assistive-technology certification or a complete composed modal/fleet gate. All workers were notified of the exact frozen hash and must verify served bytes in their final source-linked native matrices. Managed tests were not rerun for this JavaScript-only change; final combined consumer tests remain coordinator-owned. The temporary browser contexts close at harness completion, and no host/service/container lifecycle was changed.
## Bounded preactivation rollout observation
`preactivation-investigation.json` records four additional controlled native sequences against the same frozen source. With the external invoker focused when activation starts, both DOM-removal orders restore that invoker. If a synthetic sequence puts focus inside the dialog before activation starts, the adapter captures that internal control: removal before deactivation falls back to the page heading; deactivation before removal can finish on body after restoring the then-connected closing control. Safe initial Cancel, inert/body cleanup and error-free execution still occur.
This certifies capture semantics only. It does not reproduce ordinary-user timing in a composed Blazor modal, and the original UNS scratch observation had insufficient retained context to establish that cause. The coordinator accepted this as a bounded rollout note, not a reason to reopen shared source or the completed native matrices. Exact external invoker recovery in that synthetic schedule would require an explicit/pre-recorded invoker contract; no such new API or tracking hook was added. Normal initialized dialogs retain their verified opener/heading fallback behavior.
@@ -0,0 +1,59 @@
{
"purpose": "Bounded investigation only; no product source change or composed Blazor timing claim",
"sourceSha256": "7f63bd6c5181d0b70edc2e87e086fab4dfba96adabd7a19737f9b3b4f18296d5",
"nativeCases": [
{
"focusBeforeActivation": "open",
"order": "remove-before-deactivate",
"activationAccepted": true,
"safeInitialFocus": "cancel",
"afterClose": {
"id": "open",
"tag": "BUTTON",
"modalOpen": false,
"mainInert": false
},
"errors": []
},
{
"focusBeforeActivation": "open",
"order": "deactivate-before-remove",
"activationAccepted": true,
"safeInitialFocus": "cancel",
"afterClose": {
"id": "open",
"tag": "BUTTON",
"modalOpen": false,
"mainInert": false
},
"errors": []
},
{
"focusBeforeActivation": "save",
"order": "remove-before-deactivate",
"activationAccepted": true,
"safeInitialFocus": "cancel",
"afterClose": {
"id": "heading",
"tag": "H1",
"modalOpen": false,
"mainInert": false
},
"errors": []
},
{
"focusBeforeActivation": "save",
"order": "deactivate-before-remove",
"activationAccepted": true,
"safeInitialFocus": "cancel",
"afterClose": {
"id": "",
"tag": "BODY",
"modalOpen": false,
"mainInert": false
},
"errors": []
}
],
"limitations": "Controls are focused before production activate is invoked on a synthetic document. This reproduces capture semantics, not whether an ordinary user can enter that interval in a composed app."
}