This specification does not enable any new cross-site tracking capabilities. This is largely because the navigation.entries() method only returns information about the same-origin, same-frame history entries.
And then:
The storage of navigation API state in session history entries is a convenience with no tracking abilities, since the state is only accessible same-origin. That is, it provides the same power as existing APIs such as sessionStorage.
Given that this works "same-origin, same-frame", is it more correct to state that it has the same power as partitioned sessionStorage?
Currently https://wicg.github.io/navigation-api/#sp-cross-site-tracking states:
And then:
Given that this works "same-origin, same-frame", is it more correct to state that it has the same power as partitioned sessionStorage?