- From: Jonas Sicking <jonas@sicking.cc>
- Date: Sun, 12 Jul 2015 10:49:38 -0700
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: WHATWG <whatwg@whatwg.org>, Olli Pettay <olli@pettay.fi>, Majid Valipour <majidvp@chromium.org>, Ian Hickson <ian@hixie.ch>, Rick Byers <rbyers@chromium.org>
On Sat, Jul 11, 2015 at 10:51 AM, Anne van Kesteren <annevk@annevk.nl> wrote: > On Fri, Jul 10, 2015 at 10:54 PM, Majid Valipour <majidvp@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
Received on Sunday, 12 July 2015 17:50:36 UTC