This should be done in the UI process, since using the API in the WebContent process will connect to daemons we intend to block access to.
Created attachment 385692 [details] Patch
Created attachment 385696 [details] Patch
<rdar://problem/57967913>
Comment on attachment 385696 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=385696&action=review r=me > Source/WebKit/UIProcess/ios/WKContentViewInteraction.mm:2929 > + return !WebKit::currentUserInterfaceIdiomIsPad(); Incorrect indentation.
(In reply to Brent Fulgham from comment #4) > Comment on attachment 385696 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=385696&action=review > > r=me > > > Source/WebKit/UIProcess/ios/WKContentViewInteraction.mm:2929 > > + return !WebKit::currentUserInterfaceIdiomIsPad(); > > Incorrect indentation. Thanks for reviewing!
Created attachment 385929 [details] Patch
Comment on attachment 385929 [details] Patch Clearing flags on attachment: 385929 Committed r253661: <https://trac.webkit.org/changeset/253661>
Created attachment 385931 [details] Patch
(In reply to Per Arne Vollan from comment #8) > Created attachment 385931 [details] > Patch Added patch to address iOS build failure. Will land as soon as it compiles successfully on iOS.
(In reply to Per Arne Vollan from comment #9) > (In reply to Per Arne Vollan from comment #8) > > Created attachment 385931 [details] > > Patch > > Added patch to address iOS build failure. Will land as soon as it compiles > successfully on iOS. Landed https://trac.webkit.org/changeset/253663/webkit.