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.

Sign up for GitHub

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

Jump to bottom

feat: WebFrameMain no longer follows cross-origin navigations #41953

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

feat: WebFrameMain no longer follows cross-origin navigations #41953

wants to merge 1 commit into from
+38 −41

Conversation

nornagon
Copy link
Member

@nornagon nornagon commented Apr 23, 2024 •
edited

Description of Change

This stops WebFrameMain from following navigations.

Checklist

Release Notes

Notes: WebFrameMain is now tied to a single RenderFrameHost, and does not follow cross-origin navigations.

@electron-cation electron-cation bot added the new-pr 🌱 PR opened in the last 24 hours label Apr 23, 2024
@nornagon nornagon added the semver/major incompatible API changes label Apr 23, 2024
@nornagon nornagon added the target/31-x-y PR should also be added to the "31-x-y" branch. label Apr 23, 2024
@electron-cation electron-cation bot removed the new-pr 🌱 PR opened in the last 24 hours label Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
api-review/requested 🗳 semver/major incompatible API changes target/31-x-y PR should also be added to the "31-x-y" branch.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@nornagon