forked from Pissandshittium/pissandshittium
-
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.
[WebLayer] Make tab handling consistent between native and Java
There were a few inconsistencies between native and Java handling of Tabs which made writing browsertests that work on all platforms difficult if any tabs had to be created. This change fixes a few things: - Previously native code allowed tabs not attached to a browser, while Java required tabs to be attached to a browser. Now all tabs must be attached to a browser whether created in C++ or Java. - Tabs created with Tab::Create() in C++ would not work correctly if a test was running on Android. This is now fixed by forcing all tab creation to go through Browser::CreateTab(). - Adds a Browser.createTab() API in both Java and C++. - Removes Browser::RemoveTab() in favor of Browser::DestroyTab() to match the Java API. Bug: 1093899 Change-Id: I98de4715b58eb8cf601610d4eb676bb2bd9875af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2242211 Reviewed-by: Scott Violet <sky@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#777593}
- Loading branch information
1 parent
1160220
commit 9bd21d8
Showing
20 changed files
with
202 additions
and
130 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
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
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
Oops, something went wrong.