GitLab

Before this patch, it was possible to delete the render frame host
before the secure payment confirmation app, which owned an instance of
an authenticator that must outlive the render frame host. This caused a
crash.

This patch makes secure confirmation app observe the render frame host
deletion, so the app can delete the authenticator that it owns before
the associated render frame host is deleted.

The android implementation (currently behind
chrome://flags/#enable-web-platform-experimental-features flag) has been
changed to match the desktop implementation (behind origin trial in
M-86) to create the authenticator on the main frame of the web page, so
cross-origin web pages can exercise the payment credential, too.

After this patch, the authenticator is deleted before the render frame
host, which avoids the crash.

Bug: 1125614
Change-Id: I83502b1b6bf23b838211687497a6498d5c4777ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410348Reviewed-by: Danyao Wang <danyao@chromium.org>
Reviewed-by: Tommy Martino <tmartino@chromium.org>
Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#808390}