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
We have fragments that have a space at the end (outbound/22130600/po/powithspacetest%20). When trying to navigate to this fragment Backbone is stripping the trailing space in getFragment().
var M = /^[#\/]|\s+$/g;
getFragment: function(t) {
if (t == null) {
if (this._usePushState || !this._wantsHashChange) {
t = this.getPath()
} else {
t = this.getHash()
}
}
return t.replace(M, "")
},
I can understand removing the bits at the start of the fragment, but can someone explain the motivation for removing the space(s) at the end? This causes our app to fail to lookup the requested data because the part with the space is a param in the router.
Since somebody went out of his or her way to strip trailing spaces, it's probably a solution to some kind of problem, so I'll need to consult the version history in order to find the rationale. In any case, I agree it seems a bit overzealous.
We have fragments that have a space at the end (outbound/22130600/po/powithspacetest%20). When trying to navigate to this fragment Backbone is stripping the trailing space in getFragment().
I can understand removing the bits at the start of the fragment, but can someone explain the motivation for removing the space(s) at the end? This causes our app to fail to lookup the requested data because the part with the space is a param in the router.
And
The text was updated successfully, but these errors were encountered: