-
Notifications
You must be signed in to change notification settings - Fork 27.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[web][breaking] Change --web-renderer
default from auto
to canvaskit
#149826
Comments
--web-renderer
default from auto
to canvaskit
--web-renderer
default from auto
to canvaskit
) Changes the documentation of the default renderer on web. The default renderer is changing from `auto` to `canvaskit`. _This PR is mostly moving things around with no new content being added._ The PR making the code changes: flutter/flutter#149773 The issue: flutter/flutter#149826 ## Presubmit checklist - [x] This PR doesn’t contain automatically generated corrections (Grammarly or similar). - [x] This PR follows the [Google Developer Documentation Style Guidelines](https://developers.google.com/style) — for example, it doesn’t use _i.e._ or _e.g._, and it avoids _I_ and _we_ (first person). - [x] This PR uses [semantic line breaks](https://github.com/dart-lang/site-shared/blob/main/doc/writing-for-dart-and-flutter-websites.md#semantic-line-breaks) of 80 characters or fewer.
From which version will it apply ? |
Will you update the documentation here also ? |
The change hasn't landed yet, so I can't tell for sure.
Yes, that documentation is changing here: flutter/website#10722 |
…9773) - When `--web-renderer` is omitted, keep the value `null` until it later materializes to either `canvaskit` or `skwasm`. - No more hardcoded defaults anywhere. We use `WebRendererMode.defaultForJs/defaultForWasm` instead. - When in `--wasm` mode, the JS fallback is now `canvaskit` instead of `auto`. - Add test for defaulting to `skwasm` when `--wasm` is enabled. Fixes #149826
Announcement email: https://groups.google.com/g/flutter-announce/c/78pys2K3VGE |
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 |
Summary
The
--web-renderer
CLI argument's default value is changing fromauto
tocanvaskit
.Background
The
CanvasKit
renderer has come a long way since the early days of Flutter Web. Many bugs have been fixed, and the size has been reasonably decreased. We now consider theCanvasKit
renderer mature enough to be the default renderer for Flutter Web.Migration guide
We recommend using the
canvaskit
renderer, and that's why we are making it the default. But if you have a need for theauto
renderer, then you need to explicitly pass it as a CLI argument (please give us feedback on why you needauto
orhtml
renderers here).Command before migration:
Command after migration:
The text was updated successfully, but these errors were encountered: