forked from Floorp-Projects/Floorp
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bug 1810619 - Part 2: Get the content window from client.openWindow o…
…n geckoview, r=geckoview-reviewers,m_kato While writing part 1 of this patch, I noticed that the geckoview code for client.openWindow was returning the outer chrome window's BrowsingContext rather than the BrowsingContext of the primary content frame when opening a pop-up window. This meant that the native code would fail to start navigating the pop-up window (as it would try to navigate the chrome window which is not allowed). It turns out the tests were still passing because the geckoview code was actually starting the load itself, though with the wrong options and properties. In this patch I remove that call to load a URI from the Java code, and fix the code in ClientOpenWindowUtils to return the content BrowsingContext instead of the chrome one. Differential Revision: https://phabricator.services.mozilla.com/D171756
- Loading branch information
Showing
3 changed files
with
18 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters