Ah crap, think this is a bug in the client-side routing, pushing two entries into the history. I think it has to do with the query parameter. Will fix, thanks f

Ah crap, think this is a bug in the client-side routing, pushing two entries into the history. I think it has to do with the query parameter. Will fix, thanks for letting me know :)