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
Maybe there is a better name for this but I'd like to be able to change routes (e.g. clicking a link) and if the page I'm navigating to has some of the same content (e.g. header, footer, sidebar, etc.) then the inner HTML gets updated with the diff rather than loading an entirely new document.
This will cause the app to feel like a single page app from the user's perspective (even though it's really a multiple page app).
This will also help retain state for input, select, textarea, etc. as well as for more complicated things like a Google Maps rendering on the page where navigating around keeps the map loaded but other content around or on the map change as the route changes.
The text was updated successfully, but these errors were encountered:
Instead of building this, why not suggest users use a library like htmx where this is already a solved problem?
I've done this some. It isn't bad but it means that client-side interactivity must…
make a server call (latency may be too high)
can't easily leverage JSX client-side (other than building and bundling islands of interactivity yourself)
It can certainly be done but I'd prefer a more built-in solution that allows developers to consistently write JSX for server-side rendered content and interactive client-side hydrated content.
What is the feature you are proposing?
Maybe there is a better name for this but I'd like to be able to change routes (e.g. clicking a link) and if the page I'm navigating to has some of the same content (e.g. header, footer, sidebar, etc.) then the inner HTML gets updated with the diff rather than loading an entirely new document.
This will cause the app to feel like a single page app from the user's perspective (even though it's really a multiple page app).
This will also help retain state for input, select, textarea, etc. as well as for more complicated things like a Google Maps rendering on the page where navigating around keeps the map loaded but other content around or on the map change as the route changes.
The text was updated successfully, but these errors were encountered: