v0.22.0

Three false verdicts found by a red-team round of agents (#864) are fixed: a navigation Chrome refused, a fill the page undid a moment later, and a click that only changed a control's value no longer report success or "no visible effect".

Highlights

• A redirect to an app or script URL fails the navigation (#899, #890). When a server redirects to myapp://…, javascript: or view-source:, bdg <url>, page navigate, page reload, dom click on a link and dom submit print Could not load <url> (redirected to <target>): net::ERR_ABORTED and exit 80, with a suggestion that the previous page is still loaded. Before: ✓ Navigated on the old page.
• dom fill checks the value again after 2 s (#900, #892). A value the page puts back (its old value or a blank) exits 90 like an immediate mismatch; a value the page formats later passes with Page shows: <value> and data.pageValue.
• No "nothing observed" after a click that changed a form control or a same-origin iframe (#903, #891).

Changed behaviour

• dom fill takes about 2.1 s instead of about 0.25 s (the late check). --no-wait skips it.
• New exit codes where 0 was returned before: 80 for a refused redirect, 90 for a value the page puts back within 2 s.
• New wording of the "nothing happened" verdict (human output only): nothing observed within about half a second: no DOM change, requests or navigation; later results are not watched: look with bdg dom query, bdg peek or bdg dom screenshot. --json effect: "none" is unchanged; scripts that grep the old no visible effect text need the new phrase.

Known limits

• A page that replaces a filled value with an unrelated one later is still ✓ (now with Page shows:): #906.
• A value the page formats synchronously still exits 90: #901.

Install

npm install -g browser-debugger-cli

Full changelog: v0.21.0...v0.22.0