Skip to content

[browsingContext.captureScreenshot/browsingContext.print] when exactly do we take a screenshot? #1131

Description

@gsnedders

We have an inline issue in the spec, https://w3c.github.io/webdriver-bidi/#issue-b2b83ca0

webdriver-bidi/index.bs

Lines 4066 to 4070 in d636c85

1. Immediately after the next invocation of the [=run the animation frame
callbacks=] algorithm for |document|:
Issue: This ought to be integrated into the update rendering algorithm in
some more explicit way.

This I think means we should be running the steps after the relevant document in:

For each doc of docs, run the animation frame callbacks for doc, passing in the relative high resolution time given frameTimestamp and doc's relevant global object as the timestamp.

This does mean that we don't wait for other documents (e.g., child frames), and maybe more critically don't wait for:

For each doc of docs, update the rendering or user interface of doc and its node navigable to reflect the current state.

Which is the point at which the rendering actually happens.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions