Destroy secondary window in WebTestControlHost after each test
Secondary window was not destroyed after a test so the test configuration was not properly synchronised with the secondary renderer process after the first test. As a effect of that, console messages would be added to the test results for DevTools test which are configured to ignore console messages. Fixed: 1122074 Change-Id: I526d95ff7df76c386f766adbd092ef75fa9b27df Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377713 Commit-Queue: Alex Rudenko <alexrudenko@chromium.org> Auto-Submit: Alex Rudenko <alexrudenko@chromium.org> Reviewed-by:danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#801872}
Showing
Please register or sign in to comment