From af53b5fcac524bd73fab57be017d6cafc409776c Mon Sep 17 00:00:00 2001 From: issack john Date: Fri, 24 Jul 2026 16:38:57 -0700 Subject: [PATCH] Remove Safari scrollIntoView fallback from Responsive-Design ScrollToChatAndSendMessages raced the video grid's content-visibility event against a two-frame timeout, because Safari could overscroll the chat element and never fire it (#525). The underlying WebKit bug (webkit.org/b/298554) no longer reproduces, and CI now runs Safari 26.4, so the fallback is no longer needed. It also made the step finish early whenever the event took longer than two frames, which under-measured the work on any browser. Wait for the event directly instead. --- suites-experimental/suites.mjs | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/suites-experimental/suites.mjs b/suites-experimental/suites.mjs index 2f740e4bd..c86e81b35 100644 --- a/suites-experimental/suites.mjs +++ b/suites-experimental/suites.mjs @@ -264,11 +264,7 @@ export const ExperimentalSuites = freezeSuites([ page.layout(); } - // Safari can overscroll the chat element here and never send the - // video grid's contentvisibilityautostatechange event. See - // https://github.com/WebKit/Speedometer/issues/525. Remove this - // fallback once Speedometer CI runs a Safari with that WebKit fix. - await Promise.race([cvWorkComplete, new Promise((resolve) => requestAnimationFrame(() => requestAnimationFrame(resolve)))]); + await cvWorkComplete; }), new BenchmarkTestStep("IncreaseWidthIn5Steps", async (page) => { const widths = [560, 640, 704, 768, 800];