Files
lmxopcua/docs/ui-consistency/ot13-host-controls/README.md
T
2026-11-14 01:18:22 -05:00

21 lines
3.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Hosts driver controls acceptance (OT-13)
The actual Hosts page now uses the shared ModalFrame for its single outer driver-controls dialog. The panel keeps restart confirmation inline. Each presentation captures driver, Enabled and cluster identity, and busy/close callbacks reject retired presentations. Ordinary health/name refresh retains the panel; changed identity or a vanished driver retires it. The eight existing read, subscription and disposal bodies are unchanged (independently reviewed; see read-state-boundaries.json). No command API, read semantics or device behavior changes in this parent slice.
## Verification
- acceptance.log: 45 passed, zero failures/skips (six new actual parent cases, 24 panel cases and 15 prior read/diagnostic/wiring cases). The valid pre-change three-failure proof is close-render-red.log; earlier harness/reflection corrections are retained separately.
- browser-confirmation.log and browser/results.json: 12 actual Hosts contexts over synthetic services: Operator Reconnect, Operator Restart and Reader, each at 1440, 390 and native Chromium 200% (720 and 195 CSS pixels). Assertions cover one dialog, names/context, focus trap, inert background, safe inline Cancel, current captured dispatch, busy Escape/close denial, result, idle Escape and trigger restoration, no overflow and zero page errors. No real actor/device/broker mutations.
- native-zoom/: two final direct Chromium surface screenshots and measured header/footer geometry, with native Escape/trigger-return checks. The long-ID header previously clipped the chrome at 195 CSS pixels. The short title and complete wrapped body description repair that real failure without truncating identity.
- runtime-parity.json records exact current dialog-focus HTTP/source parity. Independent peer review approved source and evidence without a blocker.
The browser/ screenshots at real zoom can show a Playwright clip-framing artifact when the background document is scrolled. The final native-zoom/ images use CDP Page.captureScreenshot with fromSurface=true and captureBeyondViewport=false and show the actual viewport; intermediate zoom-captures/ and cdp-captures/ are retained as harness diagnostics. An exploratory fromSurface=false request was unsupported; no product patch follows from that capture failure.
opacity-observation.json records an actual stale-panel opacity finding handed to the final OT accessibility batch; this parent slice does not claim that separate contrast issue is resolved. VoiceOver tests are excluded at the user’s instruction; no speech-output result is claimed.
## Reproduction and cleanup
The checked-in canary mounts the production Hosts and DriverStatusPanel with synthetic health/config and a delayed typed command responder, operator/reader claims, and local in-memory data. It binds only loopback 18142. Build with a separate artifacts/output directory, then run browser.py and capture-native-zoom.py using the installed Playwright runtime. All dotnet test invocations must use infra/tools/ui-consistency/with_private_sql.py and the owned private SQL state; SQL readiness probes occur before filtering.
The fixture runtime is stopped after acceptance. No production server, existing rig container or external SQL was modified by this fixture.