having removed the "pushstate" plugin from canjs, the issue seems to be fixed.
I believe there's a bug with pushstate, or it's under-documented.
having removed the "pushstate" plugin from canjs, the issue seems to be fixed.
I believe there's a bug with pushstate, or it's under-documented.