RESOLVED INVALID296525
[GLIB] REGRESSION(297498@main): Build breaks on !ENABLE(2022_GLIB_API) 
https://bugs.webkit.org/show_bug.cgi?id=296525
Summary [GLIB] REGRESSION(297498@main): Build breaks on !ENABLE(2022_GLIB_API)
Jim Mason
Reported 2025-07-26 11:53:53 PDT
webkit/Source/WebKit/UIProcess/API/glib/WebKitJavascriptResult.cpp:40:25: error: member access into incomplete type 'WebKit::JavaScriptEvaluationResult' 40 | jsValue = result.toJSC(); | ^ webkit/Source/WebKit/UIProcess/API/glib/WebKitJavascriptResultPrivate.h:26:7: note: forward declaration of 'WebKit::JavaScriptEvaluationResult' 26 | class JavaScriptEvaluationResult; | ^ webkit/Source/WebKit/UIProcess/API/glib/WebKitJavascriptResult.cpp:53:18: error: no matching constructor for initialization of 'WebKitJavascriptResult' (aka '_WebKitJavascriptResult') 53 | new (result) WebKitJavascriptResult(serializedScriptValue); | ^ ~~~~~~~~~~~~~~~~~~~~~ webkit/Source/WebKit/UIProcess/API/glib/WebKitJavascriptResult.cpp:37:8: note: candidate constructor (the implicit copy constructor) not viable: no known conversion from 'WebCore::SerializedScriptValue' to 'const _WebKitJavascriptResult' for 1st argument 37 | struct _WebKitJavascriptResult { | ^~~~~~~~~~~~~~~~~~~~~~~ webkit/Source/WebKit/UIProcess/API/glib/WebKitJavascriptResult.cpp:37:8: note: candidate constructor (the implicit move constructor) not viable: no known conversion from 'WebCore::SerializedScriptValue' to '_WebKitJavascriptResult' for 1st argument 37 | struct _WebKitJavascriptResult { | ^~~~~~~~~~~~~~~~~~~~~~~ webkit/Source/WebKit/UIProcess/API/glib/WebKitJavascriptResult.cpp:38:14: note: candidate constructor not viable: no known conversion from 'WebCore::SerializedScriptValue' to 'WebKit::JavaScriptEvaluationResult' for 1st argument 38 | explicit _WebKitJavascriptResult(WebKit::JavaScriptEvaluationResult&& result) | ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Reverting 297498@main clears the issue.
Attachments
Add attachment proposed patch, testcase, etc.
Jim Mason
Comment 1 2025-08-09 05:08:35 PDT
Fixed by 298116@main. Closing.
Note You need to log in before you can comment on or make changes to this bug.