Sorry about that. We've identified a bug with how we handle the history state. Thanks for pointing out.