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

browser(firefox): start screencast in existing pages upon setScreencastOptions #4045

Merged
merged 1 commit into from Oct 3, 2020
Merged

browser(firefox): start screencast in existing pages upon setScreencastOptions #4045

merged 1 commit into from Oct 3, 2020

Conversation

dgozman
Copy link
Contributor

@dgozman dgozman commented Oct 2, 2020

This makes it work in persistent context.

To achieve this, we have to move screencast logic into PageTarget and
make PageHandler listen to an event.

References #3996.

…stOptions

This makes it work in persistent context.

To achieve this, we have to move screencast logic into PageTarget and
make PageHandler listen to an event.
@dgozman dgozman requested a review from yury-s October 2, 2020 16:37
@aslushnikov
Copy link
Collaborator

Why didn't it work today?

Copy link
Member

@yury-s yury-s left a comment

Choose a reason for hiding this comment

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

I'd rather change our default context logic to manually create first page, it would allow to get rid of this workaround as well as hairy logic in _loadDefaultContext. This is a bigger cross-browser change though so we can probably live with the status quo for longer.

@yury-s
Copy link
Member

yury-s commented Oct 2, 2020

Why didn't it work today?

With persistent context browser creates first page which may happen before setScreencastOptions take effect. I believe this is a general problem that first page in default context may not inherit some of the context properties.

@dgozman
Copy link
Contributor Author

dgozman commented Oct 3, 2020

I'd rather change our default context logic to manually create first page, it would allow to get rid of this workaround as well as hairy logic in _loadDefaultContext. This is a bigger cross-browser change though so we can probably live with the status quo for longer.

Yeah, we can put this into our backlog 😄

@dgozman dgozman merged commit 133de10 into microsoft:master Oct 3, 2020
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

3 participants