WebFrame could use some SPI for converting DOMNode to a JSValueRef.
Created attachment 179898 [details] patch
Created attachment 179901 [details] patch
Comment on attachment 179901 [details] patch Attachment 179901 [details] did not pass mac-ews (mac): Output: http://queues.webkit.org/results/15399125
Created attachment 179906 [details] patch
Comment on attachment 179906 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=179906&action=review > Tools/TestWebKitAPI/Tests/mac/JSWrapperForNodeInWebFrame.mm:54 > + RetainPtr<WebView> webView(AdoptNS, [[WebView alloc] initWithFrame:NSMakeRect(0, 0, 120, 200) frameName:nil groupName:nil]); You can use the adoptNS function instead for clarity. > Tools/TestWebKitAPI/Tests/mac/JSWrapperForNodeInWebFrame.mm:55 > + RetainPtr<JSWrapperForNodeFrameLoadDelegate> frameLoadDelegate(AdoptNS, [JSWrapperForNodeFrameLoadDelegate new]); Ditto. Also use alloc/init instead of new. > Tools/TestWebKitAPI/Tests/mac/JSWrapperForNodeInWebFrame.mm:82 > + JSStringRef isolatedPropertyJSString = JSStringCreateWithUTF8CString("isolatedProperty"); I think you can use a JSRetainPtr here, then you don't need to use JSStringRelease. > Tools/TestWebKitAPI/Tests/mac/JSWrapperForNodeInWebFrame.mm:88 > + JSStringRef normalPropertyJSString = JSStringCreateWithUTF8CString("normalProperty"); I think you can use a JSRetainPtr here, then you don't need to use JSStringRelease.