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
It would be nice if Backbone supported passing in statObj to window.history.pushstate via Backbone.navigate in its options. Right now if we use Backbone.navigate, the window.onpopstate callback always emits a PopStateEvent.state that is null. There is no way to distinguish between Chrome/Safari firing that event on a page load vs the user actually pressing back/forward.
The text was updated successfully, but these errors were encountered:
Hi @tomkit, thanks for opening an issue! This has been discussed before in #764, and tangentially in #1056. Backbone takes the stance that the pushState API is broken, and the only way to use it well is to ignore the first two arguments.
If you disagree with the previous reasons for ignoring those arguments, please respond to them so we can re-evaluate.
It would be nice if Backbone supported passing in statObj to window.history.pushstate via Backbone.navigate in its options. Right now if we use Backbone.navigate, the window.onpopstate callback always emits a PopStateEvent.state that is null. There is no way to distinguish between Chrome/Safari firing that event on a page load vs the user actually pressing back/forward.
The text was updated successfully, but these errors were encountered: