TheGeneralist ef8b5ac83b fix: switch uBlock loading from --browser-server to --browser-args ... The --browser-server (CDP) path caused 'Unexpected server response: 404' on macOS Chrome because simple-cdp's WebSocket upgrade to the debugger endpoint failed after Chrome started — likely a version-specific CDP endpoint shape mismatch. New approach: single-file always manages Chrome. When ARCHIVR_UBLOCK_EXT is set, --headless=new, --load-extension, and --disable-extensions-except are injected via --browser-args. single-file's browser.js prefix-strips its own conflicting flags before appending ours, so --headless=new overrides the default --headless (enabling extension support in headless). Removes allocate_free_port, wait_for_chrome_ready, run_single_file_with_server (all dead code now). Docblock updated to reflect actual behaviour and notes the --single-process caveat: uBOL's declarativeNetRequest static rulesets are expected to work (network-stack level, not service-worker), but this has not been mechanically verified under --single-process. Smoke tested on macOS (this machine): capture with --load-extension + all three browser-scripts (strip, Readability, reader-mode wrapper) produces output file correctly. Ad-blocking verification deferred to manual test with a tracker-heavy URL.		2026-07-08 09:58:36 +02:00
..
src	fix: switch uBlock loading from --browser-server to --browser-args	2026-07-08 09:58:36 +02:00
Cargo.toml	feat(singlefile): add SaveResult, favicon extraction, wait for networkidle2	2026-06-24 19:16:21 +02:00