NavigatorContentUtils was to support the custom scheme spec - https://html.spec.whatwg.org/multipage/system-state.html#custom-handlers. However, in WebKit side, no port has supported the feature in the WebKit layer after EFL port was removed. So there has been the only IDL implementation of the NavigatorContentUtils in WebCore. So let's remove the partial implementation in WebCore.
Created attachment 365523 [details] Patch
Created attachment 365525 [details] Patch
Comment on attachment 365525 [details] Patch If there is any port which has been using this feature or will use it in the future, please let me know.
Comment on attachment 365525 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=365525&action=review If we decide to implement or ship this, we can refer to the svn history. If it's just dead code, let's remove it. > Source/JavaScriptCore/ChangeLog:-138 > - * Configurations/FeatureDefines.xcconfig: > - This should be left as it was.
Comment on attachment 365525 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=365525&action=review >> Source/JavaScriptCore/ChangeLog:-138 >> - > > This should be left as it was. Right. I did a mistake when I rebase this patch.
> If we decide to implement or ship this, we can refer to the svn history. If it's just dead code, let's remove it. If someone wants to implement or ship this feature in the future, we can start to work after reverting this patch. But, as far as I know, nobody supports this feature in WebKit upstream ports now.
Created attachment 365845 [details] Patch for landing
Created attachment 365847 [details] Patch
Created attachment 365852 [details] Patch for landing
Comment on attachment 365852 [details] Patch for landing Clearing flags on attachment: 365852 Committed r243433: <https://trac.webkit.org/changeset/243433>
All reviewed patches have been landed. Closing bug.
<rdar://problem/49207736>