Repository navigation
[web] flutter-first-frame fires before the first SkWasm frame is presented #189499
Copy link
Copy link
Closed
Closed
Copy link
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work liste: wasmIssues related to the wasm build of Flutter Web.Issues related to the wasm build of Flutter Web.e: web_skwasmSkwasm rendering backend for webSkwasm rendering backend for webengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onplatform-webWeb applications specificallyWeb applications specificallyteam-webOwned by Web platform teamOwned by Web platform teamtriaged-webTriaged by Web platform teamTriaged by Web platform team
Description
Activity
- addedengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.platform-webWeb applications specificallyWeb applications specificallyhas reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work one: wasmIssues related to the wasm build of Flutter Web.Issues related to the wasm build of Flutter Web.e: web_skwasmSkwasm rendering backend for webSkwasm rendering backend for webteam-webOwned by Web platform teamOwned by Web platform team
on Jul 16, 2026 Hi @Yusufihsangorgel , thanks for the detailed report, Routing to the webteam to evaluate the issue and Pr linked #189500
Reacted by Yusuf İhsan GörgelYusufihsangorgel commented
on Jul 16, 2026 ContributorAuthorMore actionsHi @Yusufihsangorgel , thanks for the detailed report, Routing to the webteam to evaluate the issue and Pr linked #189500
Hi, Thanks.
- addedtriaged-webTriaged by Web platform teamTriaged by Web platform teamP2Important issues not at the top of the work listImportant issues not at the top of the work list
on Jul 22, 2026 - added a commit that references this issue
on Aug 11, 2026 This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on Aug 25, 2026
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work liste: wasmIssues related to the wasm build of Flutter Web.Issues related to the wasm build of Flutter Web.e: web_skwasmSkwasm rendering backend for webSkwasm rendering backend for webengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onplatform-webWeb applications specificallyWeb applications specificallyteam-webOwned by Web platform teamOwned by Web platform teamtriaged-webTriaged by Web platform teamTriaged by Web platform team
Steps to reproduce
flutter-first-framebrowser event.flutter build web --release --wasm --no-web-resources-cdn.runAppso the transition is easy to record:Expected result
The event is dispatched only after the renderer has completed the first scene,
so removing the HTML splash reveals the first Flutter frame without an
intermediate blank frame.
Actual result
With Wasm/SkWasm, the framework sends the
flutter/service_workerplatformmessage from a post-frame callback, but the web engine immediately dispatches
flutter-first-framewhilerenderer.renderScene(...)is still running.Removing the splash therefore exposes the page background before SkWasm has
finished rasterizing.
Chrome compositor screencasts of the minimal reproduction produced the same
sequence in three cold runs:
The dart2js/CanvasKit build did not produce the intermediate blank compositor
frame in the same test. The current
masterimplementation still dispatchesthe DOM event synchronously in
EnginePlatformDispatcher.This is related to the original service-worker event work in #66066 and the
first-frame hook proposal in #133454, but neither tracks the renderer-completion
race in the Wasm/SkWasm path.
Environment
The same synchronous event dispatch is present at current
master(
fc1ad955f16467c959e3cd8079b760d5af0984aa).