- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Sat, 11 Jul 2015 19:51:11 +0200
- To: Majid Valipour <majidvp@chromium.org>
- Cc: WHATWG <whatwg@whatwg.org>, Olli Pettay <olli@pettay.fi>, Ian Hickson <ian@hixie.ch>, Jonas Sicking <jonas@sicking.cc>, Rick Byers <rbyers@chromium.org>
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. Also, History isn't that full and can easily contain a bunch of properties. What's the use of a new object, can you use it independently somehow? -- https://annevankesteren.nl/
Received on Saturday, 11 July 2015 17:51:38 UTC