| Summary: | We should not kill all WebContent processes whenever the WebAuthn process crashes | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Chris Dumez <cdumez> | ||||||
| Component: | WebKit2 | Assignee: | Chris Dumez <cdumez> | ||||||
| Status: | RESOLVED FIXED | ||||||||
| Severity: | Normal | CC: | achristensen, bfulgham, ews-watchlist, ggaren, jiewen_tan, kkinnunen, webkit-bug-importer, youennf | ||||||
| Priority: | P2 | Keywords: | InRadar | ||||||
| Version: | WebKit Nightly Build | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=233001 | ||||||||
| Attachments: |
|
||||||||
|
Description
Chris Dumez
2021-11-10 16:15:17 PST
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]. |