◆ WebKit WeeklyBeta

colelao

WebCore contributor

108 commits (10mo)
View all commits on GitHub ↗

Summary

colelao's work splits between JSC's WebAssembly Memory64 implementation — Table64 across the IPInt, BBQ, and OMG tiers, SIMD support, declared memory limits, and address-type checking on table imports — and CSS value plumbing in WebCore (CSSUnitType/ValueSeparator enum refactors, the CSS Values 5 `toggle()` flag), with a smaller Find in Page cluster covering text marker caching and an iOS crash. Nothing here is classified as a security fix or hardening, but the Memory64 series is new bounds-and-indexing surface that was just switched on by default, and several commits are exactly the class of correctness gap that turns into a memory bug: an unchecked address type on table imports, oversized initial table sizes reaching compilation, and element segment expressions evaluated more than once per instance. Systematic-variant candidate: the 32-bit-to-64-bit index widening across the three Wasm tiers, where any tier that missed a bounds or type check the others got is an inconsistency worth diffing tier against tier.

Components

WebCore
31%
JSC
24%
WebKit
20%
Platform
13%
WTF
6%
Site Isolation
3%

Security Fix History

Hardening Commits

Recent Commits

1 / 8

← All Contributors