One: I badly managed the push and ended up combining the second fix with the first. Would have preferred to address the two issues separately.
Secondly I noticed that to fully implement the state=false fix, this feature test should be change so that it passes OK if pushstate is disabled. Because if we're explicitly disabling pushstate, we don't feature test for it. I think.
Lastly as I couldn't get the test runner working so was hesitant to update untested.
Sorry, two reasons.
One: I badly managed the push and ended up combining the second fix with the first. Would have preferred to address the two issues separately.
Secondly I noticed that to fully implement the `state=false` fix, this [feature test](https://github.com/MoOx/pjax/blob/master/index.js#L226) should be change so that it passes OK if pushstate is disabled. Because if we're explicitly disabling pushstate, we don't feature test for it. I think.
Lastly as I couldn't get the test runner working so was hesitant to update untested.
Pull request closed
Please reopen this pull request to perform a merge.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The logic for parsing the history option wouldn't let you set it to false and turn off history
Any reason you closed this?
Sorry, two reasons.
One: I badly managed the push and ended up combining the second fix with the first. Would have preferred to address the two issues separately.
Secondly I noticed that to fully implement the
state=falsefix, this feature test should be change so that it passes OK if pushstate is disabled. Because if we're explicitly disabling pushstate, we don't feature test for it. I think.Lastly as I couldn't get the test runner working so was hesitant to update untested.
Pull request closed