1d99429ba0
Two related bugs in the Cookbook task lifecycle: 1. "Stop all" fired kills via .click() inside a synchronous forEach but showed the success toast immediately after — the toast appeared before any of the async kill requests had been sent, giving the user false confidence the tasks were stopped. 2. The download auto-retry logic (triggered when DOWNLOAD_FAILED appears in the task output) had no way to distinguish a network interruption from a deliberate user stop. A download stopped via "Stop all" or the individual Stop button could be silently restarted up to two times by the background monitor. Fix: persist _userStopped: true to localStorage at the moment the user clicks Stop (individually) or Stop all. The auto-retry guard checks this flag before relaunching the download. The flag is written BEFORE the kill requests fire so there is no window where the monitor can race. Fixes #1458 |
||
|---|---|---|
| .. | ||
| fonts | ||
| js | ||
| lib | ||
| app.js | ||
| index.html | ||
| landing.html | ||
| login.html | ||
| manifest.json | ||
| style.css | ||
| sw.js | ||