You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A goal of app history is that you should be able to use the navigate handler to centrally convert MPA navs into SPA navs.
It'd be good to work out a detailed example of this for form submissions. In particular, given a typical post/redirect/get MPA flow where the <form> does a POST to /submission and the server then does a 303 redirect to /confirmation-page, what does that look like in a navigate handler?
If you just do event.respondWith(...), the URL will stay on /submission. So this speaks to some previous discussions about allowing a redirect-type flow within a navigate handler, so that you could do a client-side "redirect" to /confirmation-page. Then a second navigate event would fire for /confirmation-page, which would result in appropriate DOM updates showing the confirmation.
The text was updated successfully, but these errors were encountered:
A goal of app history is that you should be able to use the
navigate
handler to centrally convert MPA navs into SPA navs.It'd be good to work out a detailed example of this for form submissions. In particular, given a typical post/redirect/get MPA flow where the
<form>
does aPOST
to/submission
and the server then does a 303 redirect to/confirmation-page
, what does that look like in anavigate
handler?If you just do
event.respondWith(...)
, the URL will stay on/submission
. So this speaks to some previous discussions about allowing a redirect-type flow within anavigate
handler, so that you could do a client-side "redirect" to/confirmation-page
. Then a secondnavigate
event would fire for/confirmation-page
, which would result in appropriate DOM updates showing the confirmation.The text was updated successfully, but these errors were encountered: