← WebKit — 2026-W38
f5430ef75dd3ddb055aaedc365c64b33568b178e Use encoding-carrying CString types in Intl
not a security fix
confidence 0.13
signal score 8.97
Source/JavaScriptCore/runtime
Classified as not security-relevant.
Triage note: Sweeping type migration replacing CString/UTF8CString with ASCIICString for ICU locale strings across the Intl runtime, plus new StringImpl::asciiForCharacters / StringView::ascii helpers. The only behavioral change is canonicalizeUnicodeLocaleID() now returning {} early for non-ASCII tags instead of round-tripping utf8(); no memory-safety bug is fixed, it is correctness hardening of locale handling.
This commit was flagged by the signal scorer and reviewed by AI (not a human). It is listed only so the triage is auditable; there is no root-cause analysis because this is not a vulnerability fix.
Triage note: Sweeping type migration replacing CString/UTF8CString with ASCIICString for ICU locale strings across the Intl runtime, plus new StringImpl::asciiForCharacters / StringView::ascii helpers. The only behavioral change is canonicalizeUnicodeLocaleID() now returning {} early for non-ASCII tags instead of round-tripping utf8(); no memory-safety bug is fixed, it is correctness hardening of locale handling.
This commit was flagged by the signal scorer and reviewed by AI (not a human). It is listed only so the triage is auditable; there is no root-cause analysis because this is not a vulnerability fix.
Structural signals: smartptr_member_added (+6.47), bounds_guard (+2.0), area:Source/JavaScriptCore/runtime (+2.5), large_churn (-2.0)
Before / after
Loading diff…
On This Page