Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 780fb0070b8df789f3ad46502e15c0280c1ea4b9
https://github.com/WebKit/WebKit/commit/780fb0070b8df789f3ad46502e15c0280c1ea4b9
Author: Claudio Saavedra <[email protected]>
Date: 2026-09-28 (Mon, 28 Sep 2026)
Changed paths:
M Source/JavaScriptCore/API/glib/JSCException.cpp
M Source/WebKit/UIProcess/Inspector/wpe/WebInspectorUIProxyWPE.cpp
M Tools/TestWebKitAPI/Tests/JavaScriptCore/glib/TestJSC.cpp
Log Message:
-----------
[GLib] Use GMallocString for the strings JSCException and the WPE inspector
adopt from C APIs
https://bugs.webkit.org/show_bug.cgi?id=325402
Reviewed by Carlos Garcia Campos.
JSCException kept the name, message, source URI and backtrace it reads through
jsc_value_to_string() as GUniquePtr<char>, and computeContentHash() in the WPE
inspector did the same with g_compute_checksum_*(). Those are g_malloc'ed UTF-8
strings, so GMallocString adopts them without a copy and carries the encoding:
the getters return utf8() and the String consumers take span().
jsc_exception_report() appended the source URI and error message as Latin-1
byte spans and split the backtrace with StringView::fromLatin1(), so any
non-ASCII URI, function name or message came out mojibaked. They are now
decoded as the UTF-8 they are. TestJSC covers it with a script whose source
URI, function name and message are non-ASCII; the URI comes back
percent-encoded, the other two must come back intact.
Canonical link: https://commits.webkit.org/322035@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
