pub fn time_frames<A: ResourceApp>(
scenario: Option<&str>,
frames: usize,
) -> Result<Vec<Duration>, String>Expand description
How long each of frames frames of A’s capture of scenario takes to
sync, lay out and draw, after one frame that warms the text caches: what
a --bench command reports. Where no native runner is linked (a browser
page) there is no headless capture to time.
§Errors
Returns why the capture could not be built, or that this build has no headless capture.