Seems like they're using window.history.replaceState, which replaces the current history state. This is in contrast to window.history.pushState which adds to the stack.

I can't help but be curious if it's falling back to #hashurls for you (or something else). From my end, they've come up with a clever technique for persisting map state in a sharable way.