Refuse to type into a disabled control in the Eve client bridge (PA.f174)
`tools/eve_client_bridge.mjs`'s `set` step found the rendered control and typed into it without checking whether it was disabled, so a control a real browser would render disabled -- and refuse keystrokes into -- still silently captured a value here. That made PA.f167's own gap (a disabled control cannot be proven untestable through the bridge) cheap to close: the bridge now throws "bridge: node id <id>'s own control is disabled; a real client cannot type into it" before assigning `element.value`. BEHAVIOR CHANGE NOTE: this changes tools/eve_client_bridge.mjs's own runtime behavior -- a `set` step against a disabled control now throws instead of silently succeeding. Anyone driving the bridge directly against a surface that renders a disabled field for the node ids it types into will see a new failure where there was none before. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
parent
7052644467
commit
241b33ef2f
1 changed files with 7 additions and 0 deletions
|
|
@ -88,6 +88,13 @@ async function main() {
|
|||
? wrapper
|
||||
: wrapper.querySelector("input, textarea, select");
|
||||
if (!element) throw new Error(`bridge: node id ${nodeId} has no editable control`);
|
||||
// PA.f174: a real browser refuses keystrokes into a disabled
|
||||
// control outright -- typing into it here without this check would
|
||||
// silently capture a value no real client could ever have entered,
|
||||
// hiding exactly the gap PA.f167 named untestable.
|
||||
if (element.disabled) {
|
||||
throw new Error(`bridge: node id ${nodeId}'s own control is disabled; a real client cannot type into it`);
|
||||
}
|
||||
element.value = value;
|
||||
element.dispatchEvent(new dom.window.Event("input", { bubbles: true }));
|
||||
element.dispatchEvent(new dom.window.Event("change", { bubbles: true }));
|
||||
|
|
|
|||
Loading…
Reference in a new issue