Skip to content

Customizing how Auto mode makes its decision #48756

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

Open
SteveSandersonMS opened this issue Jun 13, 2023 · 3 comments
Open

Customizing how Auto mode makes its decision #48756

SteveSandersonMS opened this issue Jun 13, 2023 · 3 comments
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-full-stack-web-ui Full stack web UI with Blazor Pillar: Complete Blazor Web Priority:1 Work that is critical for the release, but we could probably ship without
Milestone

Comments

@SteveSandersonMS
Copy link
Member

The initial implementation of the Auto rendermode will be hardcoded to make its choice based on whether the WebAssembly files are already downloaded and cached.

Some developers may want to implement custom rules, e.g.:

  • For certain device types or network conditions, always use Server or WebAssembly (even if the user has to wait for it to download)
  • Perhaps others?

There could be a JS-side callback to allow arbitrary JS code to make the decision.

@SteveSandersonMS SteveSandersonMS added area-blazor Includes: Blazor, Razor Components feature-full-stack-web-ui Full stack web UI with Blazor labels Jun 13, 2023
@SteveSandersonMS SteveSandersonMS changed the title Configuring how Auto mode makes its decision Customizing how Auto mode makes its decision Jun 13, 2023
@mkArtakMSFT mkArtakMSFT added the enhancement This issue represents an ask for new feature or an enhancement to an existing one label Jun 13, 2023
@mkArtakMSFT mkArtakMSFT added this to the .NET 8 Planning milestone Jun 13, 2023
@ghost
Copy link

ghost commented Jun 13, 2023

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@ghost
Copy link

ghost commented Dec 20, 2023

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@Andrzej-W
Copy link

I didn't make any tests but I believe that WASM application with SIMD instructions enabled should run faster. Unfortunately SIMD instructions are not available in iOS 15.x. Currently (February 2024) there are 11% of iPhones and 18% of iPads with iOS 15 or earlier (source: https://developer.apple.com/support/app-store/). I also noticed that even simplest Blazor WASM application can be unreliable on phones with 2GB of RAM (iPhone 6s, some Android phones). These are two examples where Auto rendermode should eventually fallback to Server mode and not even load WASM files.

@mkArtakMSFT mkArtakMSFT added this to the Backlog milestone Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-full-stack-web-ui Full stack web UI with Blazor Pillar: Complete Blazor Web Priority:1 Work that is critical for the release, but we could probably ship without
Projects
None yet
Development

No branches or pull requests

4 participants