We should not kill all WebContent processes whenever the WebAuthn process crashes. This is overly aggressive. We should instead do like for the network process and have the WebProcess re-initiate the connection to the WebAuthn process when it's gone.
<rdar://83941760>
Created attachment 443876 [details] Patch
Comment on attachment 443876 [details] Patch r=me
Does this API test (or another) demonstrate that use of WebAuthn does succeed after restarting the WebAuthn process?
(In reply to Geoffrey Garen from comment #4) > Does this API test (or another) demonstrate that use of WebAuthn does > succeed after restarting the WebAuthn process? Hmm, this particular test only calls `internals.setMockWebAuthenticationConfiguration({ })` which causes the WebAuthn process to get re-launched but it indeed doesn't attempt to use WebAuthn afterwards. This seems to be the only test that involves killing the WebAuthn process... I know very little about WebAuthn :o) but I'll look into extending the test to actually use WebAuthn after the crash.
Created attachment 443887 [details] Patch
Committed r285619 (244120@main): <https://commits.webkit.org/244120@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 443887 [details].