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

Progressive enhancement of form submission & navigation #46399

Closed
mkArtakMSFT opened this issue Feb 1, 2023 · 4 comments
Closed

Progressive enhancement of form submission & navigation #46399

mkArtakMSFT opened this issue Feb 1, 2023 · 4 comments
Assignees
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 Priority:1 Work that is critical for the release, but we could probably ship without
Milestone

Comments

@mkArtakMSFT
Copy link
Member

mkArtakMSFT commented Feb 1, 2023

Normally page navigations and form submissions require a full page load. With progressive enhancement, page navigations and form submissions can be handled more efficiently by intercepting the navigation and patching the DOM. This makes the user experience much smoother and faster while preserving more of the user's context on the page. If JS functionality is not available for whatever reason the app degrades gracefully to normal page loads.

@mkArtakMSFT mkArtakMSFT added enhancement This issue represents an ask for new feature or an enhancement to an existing one area-blazor Includes: Blazor, Razor Components Priority:1 Work that is critical for the release, but we could probably ship without feature-full-stack-web-ui Full stack web UI with Blazor labels Feb 1, 2023
@mkArtakMSFT mkArtakMSFT added this to the .NET 8 Planning milestone Feb 1, 2023
@Xyncgas
Copy link

Xyncgas commented May 27, 2023

Is it essentially baking in PWA mechanisms into blazor, does it work only with Blazor's mechanism for example NavigationManager.NavigateTo() or it works for a ref linking too

@SteveSandersonMS
Copy link
Member

@Xyncgas It should work for all the things that already work with traditional Blazor interactive client-side routing (e.g., on WebAssembly). Any case where we've intercepted navigation in the past to wire it up to the client-side router, we'll also intercept to wire up to this new system.

@Xyncgas
Copy link

Xyncgas commented Jun 5, 2023

Any case where we've intercepted navigation in the past to wire it up to the client-side router, we'll also intercept to wire up to this new system.

Thanks

@SteveSandersonMS
Copy link
Member

Duplicate of #48761 and #48762

@SteveSandersonMS SteveSandersonMS closed this as not planned Won't fix, can't repro, duplicate, stale Jun 21, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Jul 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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 Priority:1 Work that is critical for the release, but we could probably ship without
Projects
None yet
Development

No branches or pull requests

3 participants