commit | 1d15cfbb98ab33a324bb96304b78c652a53a464c | [log] [tgz] |
---|---|---|
author | Rakina Zata Amni <[email protected]> | Wed Aug 05 02:32:55 2020 |
committer | Commit Bot <[email protected]> | Wed Aug 05 02:32:55 2020 |
tree | 9412931010c905f2ec6c5b643e639f9db014b8a6 | |
parent | 90ec3ea8494439da8fe0b924a24aea3cb9c1d2dd [diff] |
Update navigation content_unittests to handle same-site BrowsingInstance swap With crrev.com/c/2121522, some main-frame same-site navigations will result in a new BrowsingInstance, SiteInstance, RenderFrameHost, RenderView, etc. This CL updates expectations of content_unittests that didn't expect a change of RenderFrameHosts etc. on same-site main frame navigations. This CL does not include: - Updates for content_browsertests and non-navigation-specific tests, which are handled in crrev.com/c/2195872 and crrev.com/c/2210174. - Updates for tests under chrome/, components/ and layout tests (fixed in other CLs)) - Fix to ensure order of unload handlers on same-site cross-RFH navigations (will be fixed on a future CL) - Fix to ensure WebPreferences are carried over for cross-RFH same-site navigations (will be fixed on a future CL) For more details, see doc: https://docs.google.com/document/d/1lHdkKLUe8H6ZP6ALwj-dsus7oYcuc93HkSCHCcerItg/edit?usp=sharing Bug: 977562 Change-Id: I8cddb7e5caceea380ec413dbb446142811f0f62f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2210035 Commit-Queue: Rakina Zata Amni <[email protected]> Reviewed-by: Avi Drissman <[email protected]> Reviewed-by: Alex Moshchuk <[email protected]> Cr-Commit-Position: refs/heads/master@{#794822}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.