On Sat, Jul 11, 2015 at 10:51 AM, Anne van Kesteren <ann...@annevk.nl> wrote: > On Fri, Jul 10, 2015 at 10:54 PM, Majid Valipour <maji...@chromium.org> wrote: >> Minor bikeshed: >> I have put scrollRestoration on history.options instead of directly history >> itself in order to use history.options as an interface to contain any other >> restoration related attributes which have similar semantics (e.g., recorder >> scroll position, scale restoration, recorded scale). > > Is the History object Document-bound in all implementations? Otherwise > adding new dependent objects will be problematic security-wise.
I think we've already made that assumption given that history.state already relies on this. / Jonas