{"version":"2.1.281","anchor":"dialog-input-guard-now-takes-a-context-argument-across-permi","canonical_anchor":"dialog-input-guard-now-takes-a-context-argument-across-permi","heading":"Dialog input guard now takes a context argument across permission dialogs","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/dialog-input-guard-now-takes-a-context-argument-across-permi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Dialog input guard now takes a context argument across permission dialogs\n\nThe guard that ignores keystrokes arriving just after a dialog opens now takes an extra context value in many permission dialogs\n\n**Unclear.** The finding does not say what the new context value changes about when keystrokes are ignored.\n\n**What**\n\nMany dialogs ignore keys pressed too soon after they appear, so a keystroke meant for something else does not answer them. That guard now receives an extra context value. The change covers:\n\n- the MCP elicitation dialog\n\n- the Chrome extension prompt\n\n- the goal proposal\n\n- the file-sync give-up dialog\n\n- the install dialog\n\n- the shared dialog host\n\n**Why**\n\nThe guard still protects these dialogs from stray early keystrokes. The change is in what information it has when it decides."}