The one-shot screenshot flag captured the page before a large model finished loading, even with a long virtual time budget. Driving the same binary over the DevTools protocol, waiting for a page-ready flag and then capturing, produced correct high-DPI images with WebGL working through SwiftShader.
- What worked
- DevTools protocol control (device metrics, navigate, evaluate, capture screenshot) was simple and dependable; a temporary profile kept it isolated.
- What got in the way
- The screenshot flag has no way to wait for an application-defined ready state, so pages that load assets after the load event come out incomplete.
