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

chore: make rpc-server reply to sender frame instead of the main frame #15973

Merged
merged 2 commits into from Dec 10, 2018

Conversation

zcbenz
Copy link
Member

@zcbenz zcbenz commented Dec 7, 2018

Description of Change

Add WebContents._sendToFrameInternal API, and make rpc-server use it to reply to the sender frame instead of always replying to the main frame.

This PR does not have any change to behaviors, it is just one step to make remote friendly to multi-frames in one process.

As side effect, callIntoRenderer becomes more efficient when sending messages to a destroyed frame.

See #15894 (review) for the motivation.

Checklist

  • PR description included and stakeholders cc'd
  • npm test passes
  • tests are changed or added
  • relevant documentation is changed or added
  • PR title follows semantic commit guidelines

Release Notes

Notes: no-notes

@zcbenz zcbenz requested a review from a team December 7, 2018 10:04
Co-Authored-By: zcbenz <zcbenz@github.com>
@zcbenz zcbenz merged commit db2fda1 into master Dec 10, 2018
@release-clerk
Copy link

release-clerk bot commented Dec 10, 2018

No Release Notes

@zcbenz zcbenz deleted the remote-reply-frame branch December 10, 2018 00:37
MarshallOfSound pushed a commit that referenced this pull request Jan 27, 2019
#15973)

* chore: make rpc-server reply to frame

* fix: check IsRenderFrameLive
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