Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Window serialisation #295

Closed
wants to merge 2 commits into from
Closed

Window serialisation #295

wants to merge 2 commits into from

Conversation

andreastt
Copy link
Member

When WindowProxy objects (`window` global) are returned from scripts
evaluated by Execute Script or Execute Async Script, they are marshalled
into objects containing their associated window handles.

Top-level browsing contexts and other browsing contexts (<iframe>,
<frame>) are unique identified so that strongly typed languages can
benefit from type inference.

This reuses the same architecture we have in place for serialisation of
so-called web elements.
<p>The <dfn>web window identifier</dfn>
is the string constant "<code>window-fcc6-11e5-b4f8-330a88ab9d7f</code>".

<p>The <dfn>web frame identifier</dfn>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How would this be used? Since we can't switch to a frame like this it seems like it's not needed.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I explained in my email it lets clients infer type information so they would know not to accept a frame as argument to Switch To Window.

@AutomatedTester
Copy link
Contributor

landed in c84ab45, 484a922

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants