Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 7deaf9ddf361672fb0b5183b85c57fe0b16df3db
https://github.com/WebKit/WebKit/commit/7deaf9ddf361672fb0b5183b85c57fe0b16df3db
Author: Alex Christensen <[email protected]>
Date: 2026-06-30 (Tue, 30 Jun 2026)
Changed paths:
M Source/WebKit/UIProcess/API/Cocoa/WKUserContentController.h
M Source/WebKit/UIProcess/API/Cocoa/WKUserContentController.mm
M Tools/TestWebKitAPI/Tests/WebKit/WKWebView/JSBuffer.mm
Log Message:
-----------
Prepare to replace WKJSScriptingBuffer with NSData
https://bugs.webkit.org/show_bug.cgi?id=318234
rdar://181037054
Reviewed by Richard Robinson.
This is the first in a 2-step process to remove WKJSScriptingBuffer.
I got some API review feedback that WKJSScriptingBuffer is an odd wrapper
around NSData so why not just use NSData directly? This change will
allow Safari to switch from WKJSScriptingBuffer to NSData without breaking
binary or source compatibility. The next change will change the parameter
from id to NSData.
Test: Tools/TestWebKitAPI/Tests/WebKit/WKWebView/JSBuffer.mm
* Source/WebKit/UIProcess/API/Cocoa/WKUserContentController.h:
* Source/WebKit/UIProcess/API/Cocoa/WKUserContentController.mm:
(-[WKUserContentController addBuffer:name:contentWorld:]):
* Tools/TestWebKitAPI/Tests/WebKit/WKWebView/JSBuffer.mm:
(TEST(JSBuffer, Data)):
Canonical link: https://commits.webkit.org/316165@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
