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.

Sign up for GitHub

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

Jump to bottom

Server-side routing fallback #21

Open
jgonggrijp opened this issue Dec 7, 2016 · 0 comments
Open

Server-side routing fallback #21

jgonggrijp opened this issue Dec 7, 2016 · 0 comments
Labels
enhancement
Milestone
Gold

Comments

@jgonggrijp
Copy link
Member

jgonggrijp commented Dec 7, 2016 •
edited
Loading

Render the first visited page of any new session fully on the server side, then handle all routing after than on the client side. Also provides a fallback for JavaScript-disabled visitors and for search engines (though the latter are not going to be allowed in this particular application). Implies that all templates are employed both at the server side and the client side. Might be challenging to do in a general, non-repetitive way.
@jgonggrijp jgonggrijp added this to the Gold milestone Dec 7, 2016
jgonggrijp added a commit that referenced this issue May 21, 2018
@jgonggrijp
Revert back to hashChange routing (#33, #21)
fc5e99d 
For easier development and correctness. pushState will not work
correctly for nested routes until we take additional measure on both
client side and server side.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
Gold
Development

No branches or pull requests
1 participant
@jgonggrijp