0
Files
src/content/browser
danakj cdab6ed520 Make WebContents::IsCrashed() become false when we create the main frame
Instead of waiting for RenderProcessHost::IsReady() to become true, we
mark the WebContents as not crashed as soon as there are renderer
process objects (the RenderView and the main frame) to talk to from the
browser process. Since we communicate to these with mojo, we do not need
the legacy IPC channel to be set up which was why this used to wait for
RenderProcessHost::IsReady() to be true.

While here we move WebContents::SetIsCrashed() to WebContentsTester
since it is only public for unit tests.

R=creis@chromium.org

Bug: 1174888, 763548, 396371
Change-Id: I51f3e7f328eb9c4cd078b3f7484eced1543dfd25
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2684954
Commit-Queue: danakj <danakj@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852879}
2021-02-10 23:44:13 +00:00
..
2021-01-12 22:25:18 +00:00
2021-02-10 08:54:47 +00:00
2021-01-26 01:27:16 +00:00
2021-02-02 01:47:13 +00:00
2021-02-04 23:25:06 +00:00