Files
lmxopcua/docs/ui-consistency/ot07-touch/README.md
T

22 lines
5.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.
# OT07 touch and narrow layout acceptance
The actual baseline Raw list measured29.61px rows at1440/390 and45.78px at195 while Virtualize retained ItemSize30. The first physical assertion failed on that mismatch. Coarse-pointer expansion/menu/checkbox visuals measured18×19,28×28 and14.39px respectively.
The Raw hierarchy now owns a named, keyboard-focusable local scroll viewport capped at60dvh. Complete names and25-level indentation stay available through local horizontal scrolling. Every virtual item, including loading/error/paging rows, uses the same30px desktop/44px coarse height as ItemSize. Native matchMedia observations carry monotonic revisions and import/disposal guards; stale initial results cannot overwrite a newer capability observation. Desktop checkbox hit labels are24×30; expansion18×30 has nonoverlapping24px spacing circles relative to neighboring targets. Coarse expansion/menu/checkbox hit labels are44×44. Native checkbox appearance is preserved.
ContextMenu keeps the original Blazor-owned DOM, action delegates, disabled semantics and keyboard controller. A local adapter positions the menu in the native manual-popover top layer when supported, with a fixed visible fallback, clamping and resize observers. Observer/listener references are released when the menu unmounts. No portal clones, generic Theme component, new palette or backend contract are introduced.
Two real keyboard defects were caught in additional engine checks. WebKit emits keyboard click detail0 with nonzero coordinates, so coordinates alone failed to restore focus. Trigger click and contextmenu invokers are now explicit; physical right-click detail0 remains pointer-positioned even at0,0. A tab-focused item must use its native button click rather than also activating the menu's prior active index. The native key guard now separates that path, while focus updates the current item and contextual menu/active-descendant IDs identify the existing controls. No domain action is added or changed.
ScriptLog/FleetDiagnostics use wrapping toolbars and coarse44px controls. The diagnostics selector is constrained inside its flex field, and typed Host:port has a visible native label. Business bodies/bindings remain unchanged. ScriptLog's two header class changes were accepted and committed with OT08 (78bad3a6); OT07 owns their local geometry rules.
Verification:15focused tests pass (4invoker cases,3density lifecycle cases,8existing flatten/paging cases),0skips. The invoker regression retained1failure/2positive passes before the fix; the additional right-click origin edge is included in the green run. All later tests explicitly target owned loopback SQL through the private environment runner, including discovery. Earlier filtered runs are not claimed SQL-isolated: discovery may perform a default readiness SELECT1 before filters, though no shared SQL collection/write tests ran.
The actual Chromium16case matrix passes:1440/390/195, true coarse/tap input,500→800paging with55–62mounted rows,25-level keyboard horizontal scroll/native selection, focused selected same-DOM row through both live density changes, menu viewport resize, six toolbar scenes, real200% at720and195CSSpx/DPR2. Two affected zoom cases were repeated to correct Chrome full-page screenshot framing; viewport captures preserve actual zoom. Initial paging harness jumped before server expansion; the corrected harness waits for the real expanded scroll extent. Those logs and initial images are retained. This was one visual inspection plus bounded correction/confirmation, not a product styling loop.
Cross-repo repeatable native fixtures/results, screenshots and peer review: scadaproj/components/ui-theme/validation/ot-ui/ot07-root. The app-local DensityPilot is allowlisted/synthetic and refuses operational services. New pointer/geometry assets served byte-equal to source. Private SQL state/password and disposable browser profiles are not committed. No app deployment or real device probe occurred.
Source boundaries are recorded at this checkpoint. Later authorized OT13 caller/operation guards may intentionally change controller lifecycle code; these historical checks do not certify those later changes. [Virtualize scroll-root source](https://raw.githubusercontent.com/dotnet/aspnetcore/v10.0.0/src/Components/Web.JS/src/Virtualize.ts) explains why an unbounded horizontal-overflow ancestor would be unsafe. Human screen-reader listening remains a distinct rollout check.
Final keyboard confirmation passes in Chromium145/Firefox146/WebKit26 (exact versions in cross-repo JSON): parent Enter selects800 with one local resolution; native Tab to the second item then Enter clears with exactly one further resolution; focus returns in all3engines and no page errors occur. Explicit tabindex0 retains native item eligibility under Safari's default implicit-button preference. A controlled empty-page comparison verified that inside text/explicit controls remain tabbable; no shared ThemeShell change or release was inferred. Initial focus is owned once in the adapter, avoiding a second delayed interop focus. Return focus does not override another open menu or deliberate outside focus. Geometry/action-scope peer review accepted the checkpoint; invoker/child-key corrections have the retained red/green proofs.