Should replaceState() be included?

[tunetheweb]

Currently we include replaceState navigations (and the equivalent replace navigations from the Navigation API).

Should we?

To me a "navigation" suggests a new history entry, rather than an update of an existing entry.

Chatting with @yoavweiss I don't think we have good examples of site that do use this for soft navs (maybe because none exist?) so unless we get those and verify them I think it's questionable as to whether these should be included.