Move schemes for SchemeRegistry from WebProcessPool to LegacyGlobalSettings
Created attachment 379511 [details]
This seems wrong for the case where there are multiple webkit clients in a given process
Created attachment 383074 [details]
(In reply to Tim Horton from comment #2)
> This seems wrong for the case where there are multiple webkit clients in a
> given process
This is SPI-only, it's only used from WKContextRegisterURLSchemeAsSecure and WKContextRegisterURLSchemeAsBypassingContentSecurityPolicy, and that one client intends them to be global. If you think it would be significantly better I could deprecate those two SPIs and make a class method replacement, but I don't think that's necessary.
Comment on attachment 383074 [details]
View in context: https://bugs.webkit.org/attachment.cgi?id=383074&action=review
> + The current users of the SPI to set these only have one WebProcessPool, so they intend these settings to be global.
What if there are other WebKit clients in the same address space that have their own process pools?