Skip to content
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:tool] update --web-renderer option to account for html deprecation, and wasm support #148383

Open
stoneLee81 opened this issue May 15, 2024 · 1 comment
Labels
e: wasm Issues related to the wasm build of Flutter Web. e: web_skwasm Skwasm rendering backend for web P2 Important issues not at the top of the work list platform-web Web applications specifically team-web Owned by Web platform team triaged-web Triaged by Web platform team

Comments

@stoneLee81
Copy link

Document Link

https://docs.flutter.dev/platform-integration/web/wasm

What problem are you solving?

The command flutter build web --web-renderer auto can automatically select between html and canvaskit based on the environment. With the new Flutter version 3.22.0, Flutter Web now supports WASM. If I want the compiled web to adapt to the environment and automatically select between html, canvaskit, and wasm, can I also use the --web-renderer auto command?

@stoneLee81 stoneLee81 added the design doc Tracks a design discussion document label May 15, 2024
@darshankawar darshankawar added in triage Presently being triaged by the triage team platform-web Web applications specifically team-web Owned by Web platform team and removed design doc Tracks a design discussion document in triage Presently being triaged by the triage team labels May 15, 2024
@yjbanov yjbanov changed the title flutter build web --web-renderer auto command supports wasm? [web:tool] update --web-renderer option to account for html deprecation, and wasm support May 30, 2024
@yjbanov
Copy link
Contributor

yjbanov commented May 30, 2024

I'll take this issue as a general request for updating our web-renderer options. Two things are happening roughly in parallel, the html renderer deprecation, and introduction of wasm/skwasm. Wasm/skwasm adapts to the environment automatically. Currently, we fallback to CanvasKit because we have to fall back from both WasmGC and multi-threaded rendering at the same time.

@yjbanov yjbanov added P1 High-priority issues at the top of the work list triaged-web Triaged by Web platform team e: wasm Issues related to the wasm build of Flutter Web. e: web_skwasm Skwasm rendering backend for web P2 Important issues not at the top of the work list and removed P1 High-priority issues at the top of the work list labels May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e: wasm Issues related to the wasm build of Flutter Web. e: web_skwasm Skwasm rendering backend for web P2 Important issues not at the top of the work list platform-web Web applications specifically team-web Owned by Web platform team triaged-web Triaged by Web platform team
Projects
None yet
Development

No branches or pull requests

3 participants