"Return the result of running sessionStorage."

[annevk]

This formalism is used throughout this document but has several issues:

1. Which sessionStorage are we talking about? this's relevant global object's sessionStorage, maybe?
2. But also, wouldn't that still return the same partitioned storage as before?
3. We shouldn't call public API from internal algorithms.

[arichiv]

This is somewhat addressed (or handwaved away) in the text at the top of 2.3 but could definitely use more detail.

[annevk]

That might address 2, but not 1 or 3, and also doesn't seem like the way we want to do this long term as it makes it really hard to refactor things and generally understand the model of this.

[johannhof]

@annevk do you have any advice on how to best word this? I guess we should probably factor out the public API into an internal algorithm that can get called from both public APIs?

[annevk]

Yeah. And I guess we need partitioning to be defined so we can override that for this API somehow.