338c49b0ee
Found on the server's box after the update to 4: - Chromium called its whole window "not showing" (it took itself for minimized) while its page was on the screen; the reader (like XBot's) skipped anything not showing, so a page had no numbers. Now: visible with a place on the screen counts, containers are walked through, and only a page that isn't showing (a background tab) is left out. - Two browser profiles: Chromium's own (~/.config/chromium, where a person logged in by hand) and AnyBot's (~/.config/anybot-browser); the launcher used AnyBot's and Threads showed as logged out. One profile now (anybot-profile → Chromium's own; a box with only AnyBot's keeps that); both folders stay as they were. - The launcher's lock fd went to Chromium, which then held it for its whole life: the next start waited 30 s and failed. And its flags line had been lost in an edit. box_numbers_are_exact passes twice on a box from this image; the launcher answers in 0.09 s when the browser runs; box_screen_is_exact passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| Dockerfile | ||
| Xresources | ||
| a11y | ||
| browser | ||
| fluxbox-init | ||
| menu | ||
| overlay | ||
| start.sh | ||