As a second step in removing the XSS Auditor, let's remove the implementation of the feature in the engine, but leave the API in place so that client software doesn't see any change in interface.
<rdar://problem/83318883>
Created attachment 438722 [details] Patch
Looks like the failures are all in XSS Auditor tests, which makes sense.
Created attachment 438759 [details] Patch
Created attachment 438835 [details] Patch
Created attachment 438841 [details] Patch
*** Bug 35802 has been marked as a duplicate of this bug. ***
*** Bug 54110 has been marked as a duplicate of this bug. ***
*** Bug 57852 has been marked as a duplicate of this bug. ***
*** Bug 34061 has been marked as a duplicate of this bug. ***
Comment on attachment 438841 [details] Patch r=me
*** Bug 112764 has been marked as a duplicate of this bug. ***
*** Bug 189551 has been marked as a duplicate of this bug. ***
Will land once the API tests complete.
*** Bug 214735 has been marked as a duplicate of this bug. ***
*** Bug 67818 has been marked as a duplicate of this bug. ***
Committed r282847 (241978@main): <https://commits.webkit.org/241978@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 438841 [details].