experiments in a post-browser web

fix(desktop): seed hybrid-overlay app-active gate true in headless (Electron 43) master

Electron 43's app.isActive() reports false under the headless/accessory activation policy (the app is never frontmost in CI). initHybridOverlay consulted it at init and so seeded appActive=false, disarming the app-active gate before any test drives a resign/become transition: click-capture never armed (capture gated on appActive), Cmd+L never focused the overlay, and the R1 baseline read appActive=false. That broke 3 hybrid-overlay specs under the E43 migration. Keep the documented "normally active at init" seed in headless; consult app.isActive() only for a real (non-headless) app, where a freshly-launched window genuinely is frontmost. peek 06d363fc.


Author burrito.space Date Commit 77f905e3 Parent aeb3836e Change ID tquvvnol
+11 -1
1 changed file