Last Updated: 11 Aug 2016 19:04 by Marc Simkin
Marc Simkin
Created on: 11 Aug 2016 16:50
Category: SPA
Type: Feature Request
html5 routing
The routing framework should allow the developer to choose either the legacy # base routing scheme or the new HTML5 routing and History API.

This would make the porting of applications from other frameworks (AngularJS, Backbone, etc) that already support HTML5 routing easier.
Marc Simkin
Posted on: 11 Aug 2016 19:04
Found it.  It is called push state.  Maybe the documentation needs to be updated to specifically state that this will configure routing to be HTML5 compatible.
Marc Simkin
Posted on: 11 Aug 2016 18:54
I don't see anything in the documentation about not using a hash (#) or hash bang.  I do see support for the history api.
Posted on: 11 Aug 2016 18:42
This is available - check the API reference of the router.