Enloop v0.5.9

Capture, asked in front of the run

The Capture console output and Capture failed requests checkboxes now sit directly above Start run on a case screen, and at the top of a free run. They were previously only in Settings — a screen away from the run they apply to, and away from the moment anyone actually thinks "I should keep the console for this".

They are the same setting in all three places, not three settings: capture is a browser-wide content-script registration, so ticking a box applies to every run from then on. The panel says so, and — while either box is on — says the other thing worth knowing: leave them off when you are not using them, because every console call and every request on a granted site then runs through a wrapper.

The "reload the page to start capturing" notice gained a ⓘ explaining why that is a technical limitation rather than a preference: Chrome installs the wrappers only at the very start of a page load, before the page's own scripts, so it cannot reach a page that has already loaded. Turning capture off needs no reload.

Two fixes came with it: pressing Reload page in Settings now clears the notice (nothing re-checked before, so it stayed up looking stuck), and a run already in progress follows the setting instead of holding its own copy.

Also in this build, from the two commits since v0.5.8: the case grammar spec now ships inside the plugin, with a linter and a validator CLI, so the authoring skills no longer need a clone of this repo.

Install

Enloop is not in the Chrome Web Store. Download enloop-0.5.9.zip, unzip it somewhere you intend to keep, then chrome://extensions → Developer mode → Load unpacked → select the unzipped folder (the one with manifest.json directly inside it).

Upgrading: replace the contents of your existing folder with this zip's, then press Reload on the Enloop card at chrome://extensions and reopen the side panel. Settings → About should read v0.5.9.